| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [patch 0/6] xenblk: Add O_DIRECT and O_SYNC support.
|
To: |
Jens Axboe <jens.axboe@xxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx> |
|
Subject: |
Re: [Xen-devel] [patch 0/6] xenblk: Add O_DIRECT and O_SYNC support. |
|
From: |
Keir Fraser <keir.fraser@xxxxxxxxxxxxx> |
|
Date: |
Wed, 05 Nov 2008 21:02:36 +0000 |
|
Cc: |
Xen-devel@xxxxxxxxxxxxxxxxxxx, kurt.hackel@xxxxxxxxxx, shinya.narahara@xxxxxxxxxx, Joe Jin <joe.jin@xxxxxxxxxx>, greg.marsden@xxxxxxxxxx, wen.gang.wang@xxxxxxxxxx |
|
Delivery-date: |
Wed, 05 Nov 2008 13:02:47 -0800 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<20081105201649.GQ21867@xxxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
Thread-index: |
Ack/idQzEsHvl6t9Ed27mwAWy6hiGQ== |
|
Thread-topic: |
[Xen-devel] [patch 0/6] xenblk: Add O_DIRECT and O_SYNC support. |
|
User-agent: |
Microsoft-Entourage/11.4.0.080122 |
On 5/11/08 20:16, "Jens Axboe" <jens.axboe@xxxxxxxxxx> wrote:
>>> Does blkback propagate unplug events downwards?
>>
>> Not sure what that means. blkback does its own limited queue plugging to try
>> to develop usefully schedulable batches of I/O. There's no concept of
>> plugging across the blkfront/blkback interface.
>
> So once you leave your queuing loop, you unplug the below device? Or
> just point me at the source...
The tree's at http://xenbits.xensource.com/linux-2.6.18-xen.hg
You can clone it or browse it there.
The medium- to long-term issue is just to make sure that Jeremy's port of
blkback into upstream Linux (which he's probably working on at the moment)
doesn't perpetuate the bio violations. But I guess we should fix 2.6.18 too
since others base their own Xen patchsets on it still (e.g., for dom0
support).
Thanks,
Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home