WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] make blkfront/blktagp2 respect the elevator=xyz

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] make blkfront/blktagp2 respect the elevator=xyz command line option
From: Daniel Stodden <daniel.stodden@xxxxxxxxxx>
Date: Fri, 9 Oct 2009 11:33:19 -0700
Cc: Paolo Bonzini <pbonzini@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 09 Oct 2009 11:33:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C6F529F2.170DA%keir.fraser@xxxxxxxxxxxxx>
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>
References: <C6F529F2.170DA%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 2009-10-09 at 12:57 -0400, Keir Fraser wrote:
> Should we bother to call elevator_init() at all? The call has been in that
> 2.6 driver forever, and there's probably no great reason. Shall we just kill
> it?
> 
>  -- Keir

In blktap2, I'm not convinced that going with the system default
scheduler should be the common choice. Let's go for "noop" vs a module
option, if people indeed want to experiment with it.

For blkfront, I agree. Is there a use case for defaulting to something
different than a system default?

Daniel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel