similar to: [PATCH] Add BLKIF_OP_FLUSH_DISKCACHE

add segring support in blkback Signed-off-by: Ronghui Duan <ronghui.duan@intel.com> diff --git a/drivers/block/xen-blkback/blkback.c b/drivers/block/xen-blkback/blkback.c index 45eda98..0bbc226 100644 --- a/drivers/block/xen-blkback/blkback.c +++ b/drivers/block/xen-blkback/blkback.c @@ -60,6 +60,10 @@ static int xen_blkif_reqs = 64; module_param_named(reqs, xen_blkif_reqs, int, 0);

Dear list, This is the V4 of the trim support for xen-blkfront/blkback, Now we move BLKIF_OP_TRIM to BLKIF_OP_DISCARD, and dropped all "trim" stuffs in the patches, and use "discard" instead. Also we updated the helpers of blkif_x86_{32|64}_request or we will meet problems using a non-native protocol. And this patch has been tested with both SSD and raw file, with SSD we will

Hi all, I add a blkback QoS patch. You can config(dynamic/static) different I/O speed for different VM disk by this patch. ---------------------------------------------------------------------------- diff -urNp blkback/blkback.c blkback-qos/blkback.c --- blkback/blkback.c 2011-06-22 07:54:19.000000000 +0800 +++ blkback-qos/blkback.c 2011-06-22 07:53:18.000000000 +0800 @@ -44,6 +44,11 @@

Hi all, I add a blkback QoS patch. You can config(dynamic/static) different I/O speed for different VM disk by this patch. ---------------------------------------------------------------------------- diff -urNp blkback/blkback.c blkback-qos/blkback.c --- blkback/blkback.c 2011-06-22 07:54:19.000000000 +0800 +++ blkback-qos/blkback.c 2011-06-22 07:53:18.000000000 +0800 @@ -44,6 +44,11 @@

This patch implements persistent grants for the xen-blk{front,back} mechanism. The effect of this change is to reduce the number of unmap operations performed, since they cause a (costly) TLB shootdown. This allows the I/O performance to scale better when a large number of VMs are performing I/O. Previously, the blkfront driver was supplied a bvec[] from the request queue. This was granted to

# HG changeset patch # User john.levon@sun.com # Date 1161090606 25200 # Node ID c6bfe43048f3becda6966deceb7b70baea833b7c # Parent 03d4223c846b14fc415cfd05d970c7b4d688fddb Many of the tools use C99 features such as bool, or expect certain functions. Fix the CFLAGS to enable these on Solaris. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/config/SunOS.mk b/config/SunOS.mk ---

Fix for pygrub path on Solaris. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/python/xen/xend/XendDomainInfo.py b/tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py +++ b/tools/python/xen/xend/XendDomainInfo.py @@ -37,7 +37,7 @@ from xen.util.blkif import blkdev_uname_ from xen.util.blkif import blkdev_uname_to_file from xen.util

refactoring balback Signed-off-by: Ronghui Duan <ronghui.duan@intel.com<mailto:ronghui.duan@intel.com>> diff --git a/drivers/block/xen-blkback/blkback.c b/drivers/block/xen-blkback/blkback.c index 73f196c..b4767f5 100644 --- a/drivers/block/xen-blkback/blkback.c +++ b/drivers/block/xen-blkback/blkback.c @@ -64,6 +64,11 @@ MODULE_PARM_DESC(reqs, "Number of blkback requests to

Also remove unused xenbus_{,un}map_ring(), adjust types, and clean up header inclusion. Signed-off-by: Jan Beulich <jbeulich@novell.com> --- a/drivers/xen/blkback/blkback.c +++ b/drivers/xen/blkback/blkback.c @@ -41,6 +41,8 @@ #include <linux/list.h> #include <linux/delay.h> #include <xen/balloon.h> +#include <xen/evtchn.h> +#include <xen/gnttab.h>

Hi *, when I try to start this config kernel = "/boot/vmlinuz-2.6.11-xenU" memory = 128 name = "Virtual1" vif = [ ''mac=aa:00:00:00:00:11, bridge=xen-br0'' ] disk = [ ''phy:vg00/domu01_lv,sda1,w'' ] root = "/dev/sda1 ro" extra = "4" I get this errors in xend.log (tried two times): [2005-05-23 13:37:22 xend] INFO

I am using the srpm from http://xenbits.xensource.com/kernels/rhel3x/kernel-2.4.21-47.0.1.EL.xs0.3.5. 15.src.rpm (I get the same issue using the binary RPM) the dom0 is running 3.0.3_0 Upon booting the DomU, (the DomU has been passed phy:/dev/sda6, which has been partitioned using qemu) I get the following ioctl errors. ioctl 0000126c not supported by XL blkif ioctl 0000126c not supported

Hey guys, Pasi mentioned on Li''s (and Owen''s) patches which provide TRIM/UNMAP support to the Linux backend/frontend that: " Isn''t the generic name for this functionality "discard" in Linux? and "trim" being the ATA specific discard-implementation, and "scsi unmap" the SAS/SCSI specific discard-implementation? Just

Hi! I just wanted to ask if anyone managed to get "ordinary" HFC-S ISDN cards with the zaphfc driver running in a Xen3 DomU. I am referring to this post ( http://lists.xensource.com/archives/html/xen-users/2007-04/msg00202.html ), which perfectly describes my problem and I am therefore going to simply copy-and-paste it here: ----------- snip ------------> Hi, I''m

I am proposing these two patches for 3.2. They allow the backend to process the REQ_FUA request as well. Previous to these patches it only did REQ_FLUSH. There is also a bug-fix for the logic of how barrier/flushes were handled. The patches are based on a branch which also has ''feature-discard'' patches, so they won''t apply nativly on top of 3.1-rc5. Please review and

I am trying to start a large number of SMP domains (> 50). However, I am unable to create more than 7 domains. When I try creating the 8th domain, I get this error: Using config file "myconf7". VIRTUAL MEMORY ARRANGEMENT: Loaded kernel: 0xc0100000->0xc0344c24 Init. ramdisk: 0xc0345000->0xc0345000 Phys-Mach map: 0xc0345000->0xc0347800 Page tables:

Moi! I upgraded Xen-2.0.1 to Xen-2.0.5 (testing) and everything compiled cleanly. I''m still able to boot dom0 and start domUs but networking doesn''t work anymore. xen-br0 appears in dom0, but vif-interfaces now only when ifconfig -a is used. Interface appears in domU and all seems to be fine, except no any data doesn''t move in any direction. I can''t even ping

When backend disconnect, sync IO requests to the disk. Signed-off-by: Joe Jin <joe.jin@oracle.com> Cc: Jens Axboe <jaxboe@fusionio.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: Ian Campbell <Ian.Campbell@eu.citrix.com> --- drivers/block/xen-blkback/xenbus.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/drivers/block/xen-blkback/xenbus.c

I''m finding I cannot use the vif parameter with ''bridge'' only For example: vif=bridge=xen-br2 This errors out: [2005-09-30 14:23:55 xend] DEBUG (XendDomainInfo:1107) Creating vif dom=16 vif=0 mac=None [2005-09-30 14:23:55 xend] DEBUG (XendDomainInfo:665) Destroying vifs for domain 16 [2005-09-30 14:23:55 xend] DEBUG (XendDomainInfo:674) Destroying vbds for domain

Hi everyone, as what I''ve learned form this link<http://wiki.xensource.com/xenwiki/blktap>, i know that when i specify tap:aio I’m actually using the blktap driver and finally using "tapdisk" to wirite to raw image file. but the truth is even when i delete /usr/sbin/tapdisk the domU can still boot on my machine with tap:aio protocol after a deeper look into the scene,