search for: write_barri

...= 1; @@ -367,14 +416,14 @@ handle_request: switch (req.operation) { case BLKIF_OP_READ: blkif->st_rd_req++; - ret = dispatch_rw_block_io(blkif, &req, pending_req); + ret = dispatch_rw_block_io(blkif, &req, pending_req,&last_done_nr_sects); break; case BLKIF_OP_WRITE_BARRIER: blkif->st_br_req++; /* fall through */ case BLKIF_OP_WRITE: blkif->st_wr_req++; - ret = dispatch_rw_block_io(blkif, &req, pending_req); + ret = dispatch_rw_block_io(blkif, &req, pending_req,&last_done_nr_sects); break; case BLKIF_OP_PACKET: DPRINTK...

...= 1; @@ -367,14 +416,14 @@ handle_request: switch (req.operation) { case BLKIF_OP_READ: blkif->st_rd_req++; - ret = dispatch_rw_block_io(blkif, &req, pending_req); + ret = dispatch_rw_block_io(blkif, &req, pending_req,&last_done_nr_sects); break; case BLKIF_OP_WRITE_BARRIER: blkif->st_br_req++; /* fall through */ case BLKIF_OP_WRITE: blkif->st_wr_req++; - ret = dispatch_rw_block_io(blkif, &req, pending_req); + ret = dispatch_rw_block_io(blkif, &req, pending_req,&last_done_nr_sects); break; case BLKIF_OP_PACKET: DPRINTK...

...r policies to schedule BIOs. > - Policies which fits SSD. > e.g.) > - Guarantee response time. > - Guarantee throughput. > - Policies which fits Highend Storage or hardware raid storage. > - Some LUNs may share the same bandwidth. > - Support WRITE_BARRIER when the device-mapper layer supports it. > - Implement the algorithm of dm-ioband in the block I/O layer > experimentally. > > bio-cgroup > ========== > > Bio-cgroup is a BIO tracking mechanism, which is implemented on the > cgroup memory subsystem. With the mecha...

...r policies to schedule BIOs. > - Policies which fits SSD. > e.g.) > - Guarantee response time. > - Guarantee throughput. > - Policies which fits Highend Storage or hardware raid storage. > - Some LUNs may share the same bandwidth. > - Support WRITE_BARRIER when the device-mapper layer supports it. > - Implement the algorithm of dm-ioband in the block I/O layer > experimentally. > > bio-cgroup > ========== > > Bio-cgroup is a BIO tracking mechanism, which is implemented on the > cgroup memory subsystem. With the mecha...

I have some Xen systems running Xen-4.1.1, dom0 linux-2.6.38 patched (it''s gentoo''s xen-sources) and domUs running linux-3.0.4 (vanilla sources from kernel.org). Block devices are phy on LVM2 volumes on DRBD-8.3.9 devices. Not immediately after boot, but after some I/O load on the disks I start seeing these in the domUs: blkfront: barrier: empty write xvdb1 op failed blkfront:

...sn't so active. TODO: - Other policies to schedule BIOs. - Policies which fits SSD. e.g.) - Guarantee response time. - Guarantee throughput. - Policies which fits Highend Storage or hardware raid storage. - Some LUNs may share the same bandwidth. - Support WRITE_BARRIER when the device-mapper layer supports it. - Implement the algorithm of dm-ioband in the block I/O layer experimentally. bio-cgroup ========== Bio-cgroup is a BIO tracking mechanism, which is implemented on the cgroup memory subsystem. With the mechanism, it is able to determine which cgro...

...sn't so active. TODO: - Other policies to schedule BIOs. - Policies which fits SSD. e.g.) - Guarantee response time. - Guarantee throughput. - Policies which fits Highend Storage or hardware raid storage. - Some LUNs may share the same bandwidth. - Support WRITE_BARRIER when the device-mapper layer supports it. - Implement the algorithm of dm-ioband in the block I/O layer experimentally. bio-cgroup ========== Bio-cgroup is a BIO tracking mechanism, which is implemented on the cgroup memory subsystem. With the mechanism, it is able to determine which cgro...

...sn't so active. TODO: - Other policies to schedule BIOs. - Policies which fits SSD. e.g.) - Guarantee response time. - Guarantee throughput. - Policies which fits Highend Storage or hardware raid storage. - Some LUNs may share the same bandwidth. - Support WRITE_BARRIER when the device-mapper layer supports it. - Implement the algorithm of dm-ioband in the block I/O layer experimentally. bio-cgroup ========== Bio-cgroup is a BIO tracking mechanism, which is implemented on the cgroup memory subsystem. With the mechanism, it is able to determine which cgro...

...and2 default group 10 Remove band devices ------------------- Remove the band devices when no longer used. # dmsetup remove band1 # dmsetup remove band2 TODO ======================== - Cgroup support. - Control read and write requests separately. - Support WRITE_BARRIER. - Optimization. - More configuration tools. Or is the dmsetup command sufficient? - Other policies to schedule BIOs. Or is the weight policy sufficient? Thanks, Ryo Tsuruta

...and2 default group 10 Remove band devices ------------------- Remove the band devices when no longer used. # dmsetup remove band1 # dmsetup remove band2 TODO ======================== - Cgroup support. - Control read and write requests separately. - Support WRITE_BARRIER. - Optimization. - More configuration tools. Or is the dmsetup command sufficient? - Other policies to schedule BIOs. Or is the weight policy sufficient? Thanks, Ryo Tsuruta

Patrick, there following patches fix xenpaging for me. Granttable handling is incomplete. If a page is gone, a GNTST_eagain should be returned to the caller to inidcate the hypercall has to be retried after a while, until the page is available again. Please review. Olaf _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

...xn0: Ethernet address: 00:16:3e:0b:a4:b1 xenbusb_back0: <Xen Backend Devices> on xenstore0 xctrl0: <Xen Control Device> on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 xbd0: 20480MB <Virtual Block Device> at device/vbd/51712 on xenbusb_front0 xbd0: features: flush, write_barrier xbd0: synchronize cache commands enabled. GEOM: new disk xbd0 random: unblocking device. Netvsc initializing... SMP: AP CPU #5 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #4 Launched! TSC timecounter discards lower 1 bi...

Hi everyone, This is dm-ioband version 0.0.3 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. Changes since 0.0.2 (23rd January): - Ported to linux-2.6.24. - Rename the name of this device-mapper device as "ioband." - The output format of "dmsetup

Hi everyone, This is dm-ioband version 0.0.3 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. Changes since 0.0.2 (23rd January): - Ported to linux-2.6.24. - Rename the name of this device-mapper device as "ioband." - The output format of "dmsetup

Hi everyone, This is dm-ioband version 0.0.3 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. Changes since 0.0.2 (23rd January): - Ported to linux-2.6.24. - Rename the name of this device-mapper device as "ioband." - The output format of "dmsetup