From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] make blkfront/blktagp2 respect the elevator=xyz command line option
Date: Fri, 09 Oct 2009 17:57:06 +0100 [thread overview]
Message-ID: <C6F529F2.170DA%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <1255105914-2570-1-git-send-email-pbonzini@redhat.com>
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
On 09/10/2009 17:31, "Paolo Bonzini" <pbonzini@redhat.com> wrote:
> For some workloads, CFQ has better performance than the no-op scheduler
> that is forced by the blkfront driver. The only way to set a different
> scheduler is the sysfs interface, because elevator_init is called
> unconditionally. This patch allows one to use "elevator=cfq" as well.
>
> While one could argue that the driver's behavior is expected (after all
> "elevator=cfq" is the default and should not have any effect), the
> do-what-I-mean behavior implemented by this patch is more logical.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> block/elevator.c | 3 ++-
> drivers/xen/blkfront/vbd.c | 11 ++++++-----
> drivers/xen/blktap2/device.c | 11 ++++++-----
> 3 files changed, 14 insertions(+), 11 deletions(-)
>
> diff --git a/block/elevator.c b/block/elevator.c
> --- a/block/elevator.c
> +++ b/block/elevator.c
> @@ -132,7 +132,8 @@
> eq->elevator_data = data;
> }
>
> -static char chosen_elevator[16];
> +char chosen_elevator[16];
> +EXPORT_SYMBOL_GPL(chosen_elevator);
>
> static int __init elevator_setup(char *str)
> {
> diff --git a/drivers/xen/blkfront/vbd.c b/drivers/xen/blkfront/vbd.c
> --- a/drivers/xen/blkfront/vbd.c
> +++ b/drivers/xen/blkfront/vbd.c
> @@ -208,6 +208,8 @@
> /* XXX: release major if 0 */
> }
>
> +extern char chosen_elevator[];
> +
> static int
> xlvbd_init_blk_queue(struct gendisk *gd, u16 sector_size)
> {
> @@ -217,11 +219,10 @@
> if (rq == NULL)
> return -1;
>
> -#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,10)
> - elevator_init(rq, "noop");
> -#else
> - elevator_init(rq, &elevator_noop);
> -#endif
> + /* Always respect the user's explicitly chosen elevator, but otherwise
> + pick a different default than CONFIG_DEFAULT_IOSCHED. */
> + if (!*chosen_elevator)
> + elevator_init(rq, "noop");
>
> /* Hard sector size and max sectors impersonate the equiv. hardware. */
> blk_queue_hardsect_size(rq, sector_size);
> diff --git a/drivers/xen/blktap2/device.c b/drivers/xen/blktap2/device.c
> --- a/drivers/xen/blktap2/device.c
> +++ b/drivers/xen/blktap2/device.c
> @@ -1034,6 +1034,8 @@
> return 0;
> }
>
> +extern char chosen_elevator[];
> +
> int
> blktap_device_create(struct blktap *tap)
> {
> @@ -1078,11 +1080,10 @@
> if (!rq)
> goto error;
>
> -#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,10)
> - elevator_init(rq, "noop");
> -#else
> - elevator_init(rq, &elevator_noop);
> -#endif
> + /* Always respect the user's explicitly chosen elevator, but otherwise
> + pick a different default than CONFIG_DEFAULT_IOSCHED. */
> + if (!*chosen_elevator)
> + elevator_init(rq, "noop");
>
> gd->queue = rq;
> rq->queuedata = dev;
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2009-10-09 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 16:31 [PATCH] make blkfront/blktagp2 respect the elevator=xyz command line option Paolo Bonzini
2009-10-09 16:57 ` Keir Fraser [this message]
2009-10-09 18:33 ` Daniel Stodden
2009-10-09 19:22 ` Keir Fraser
2009-10-12 8:34 ` Paolo Bonzini
2009-10-12 19:32 ` Konrad Rzeszutek Wilk
2009-10-13 7:48 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C6F529F2.170DA%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=pbonzini@redhat.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.