This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: Is QoS of virtual disk not necessary?

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] Re: Is QoS of virtual disk not necessary?
From: Andi Kleen <andi@xxxxxxxxxxxxxx>
Date: Fri, 24 Aug 2007 22:53:50 +0200
Cc: Satoshi Uchida <s-uchida@xxxxxxxxxxxxx>, Andi Kleen <andi@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 30 Aug 2007 02:57:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C2F4D6B6.148D3%Keir.Fraser@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: <p73d4xcyhbo.fsf@xxxxxxxxxxxxxx> <C2F4D6B6.148D3%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/
On Fri, Aug 24, 2007 at 06:40:54PM +0100, Keir Fraser wrote:
> On 24/8/07 18:26, "Andi Kleen" <andi@xxxxxxxxxxxxxx> wrote:
> >> Another nice thing would be that if we do not use CFQ then we do not need a
> >> kernel thread per VBD.
> > 
> > It would be probably easy to extend CFQ2 to use an user passed identifier
> > instead of per task for sharing if that's your goal. For a kernel driver
> > like blkback you could just switch around multiple current->io_contexts.
> Does current->io_context get latched before submit_bh() (or whatever similar
> function it is we use) returns? Is this true even in older 2.6 kernels with
> old CFQ?

It obviously has to because you could exit in the next call.
The context is reference counted and lazily freed.


Xen-devel mailing list