|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] poor domU VBD performance.
To: |
Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> |
Subject: |
Re: [Xen-devel] poor domU VBD performance. |
From: |
Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> |
Date: |
Thu, 31 Mar 2005 20:10:58 +0100 |
Cc: |
Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Xen development list <xen-devel@xxxxxxxxxxxxxxxxxxx>, Kurt Garloff <garloff@xxxxxxx>, Philip R Auld <pauld@xxxxxxxxxxx>, Vincent Hanquez <tab@xxxxxxxxx>, Jens Axboe <axboe@xxxxxxx>, Christian Limpach <Christian.Limpach@xxxxxxxxxxxx> |
Delivery-date: |
Thu, 31 Mar 2005 19:12:23 +0000 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<f2ccf7f627278ae1b5169fae8bc21eda@xxxxxxxxxxxx> |
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<A95E2296287EAD4EB592B5DEEFCE0E9D1E3930@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20050331070514.GH9204@xxxxxxx> <20050331071043.GI9204@xxxxxxx> <63537e2b84ddbba6cb3d970f73c6ab35@xxxxxxxxxxxx> <20050331081900.GK9204@xxxxxxx> <20050331143312.GB13179@xxxxxxxxxxxxxxxxxx> <20050331153449.GE12579@xxxxxxxxxxxxxxxxx> <20050331165305.GA13875@xxxxxxxxxxxxxxxxxx> <20050331180151.GT9204@xxxxxxx> <20050331184309.GC13875@xxxxxxxxxxxxxxxxxx> <f2ccf7f627278ae1b5169fae8bc21eda@xxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
On 31 Mar 2005, at 20:07, Keir Fraser wrote:
Since all the bio's that I queue up in a single invocation of
dispatch_rw_block_io() will actually be adjacent to each other
(because they're all from the same scatter-gather list)
I should add: I know that the code makes it look like each s-g element
might map somewhere entirely different from the previous one, but we no
longer support that mode of operation. Each VBD now always maps onto a
single, entire block device or partition.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] poor domU VBD performance., (continued)
- Re: [Xen-devel] poor domU VBD performance., Keir Fraser
- Re: [Xen-devel] poor domU VBD performance., Andrew Theurer
- Re: [Xen-devel] poor domU VBD performance., Jens Axboe
- Re: [Xen-devel] poor domU VBD performance., Philip R Auld
- Re: [Xen-devel] poor domU VBD performance., Philip R Auld
- Re: [Xen-devel] poor domU VBD performance., Jens Axboe
- Re: [Xen-devel] poor domU VBD performance., Philip R Auld
- Re: [Xen-devel] poor domU VBD performance., Keir Fraser
- Re: [Xen-devel] poor domU VBD performance.,
Keir Fraser <=
- Re: [Xen-devel] poor domU VBD performance., Jens Axboe
- Re: [Xen-devel] poor domU VBD performance., Jens Axboe
RE: [Xen-devel] poor domU VBD performance., Ian Pratt
Re: [Xen-devel] poor domU VBD performance., Andrew Theurer
RE: [Xen-devel] poor domU VBD performance., Ian Pratt
|
|
|
|
|