public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: "Fernando Luis Vázquez Cao" <fernando@oss.ntt.co.jp>
Cc: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] virtio_blk: use noop elevator by default
Date: Tue, 26 Aug 2008 16:39:01 +0200	[thread overview]
Message-ID: <20080826143900.GM20055@kernel.dk> (raw)
In-Reply-To: <1219754894.7235.44.camel@sebastian.kern.oss.ntt.co.jp>

On Tue, Aug 26 2008, Fernando Luis Vázquez Cao wrote:
> Hi Rusty,
> 
> Would it make sense to use noop by default? After all we do not know
> what is behind the backend driver and the hypervisor is likely to do its
> own scheduling anyway. I guess this is the reason the Xen guys took this
> approach.
> 
> What do you think about the patch below?

I plan to include some variant of disk profiling for 2.6.28 which will
let eg CFQ turn off idling for such device types, I think that is a
better solution.

-- 
Jens Axboe


  reply	other threads:[~2008-08-26 14:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 12:48 [PATCH] virtio_blk: use noop elevator by default Fernando Luis Vázquez Cao
2008-08-26 14:39 ` Jens Axboe [this message]
2008-08-27  5:14   ` Fernando Luis Vázquez Cao
2008-10-27  9:44     ` [PATCH 1/3] block: add queue flag for paravirt frontend drivers Fernando Luis Vázquez Cao
2008-10-27 12:56       ` Jens Axboe
2008-11-04 23:23         ` Jeremy Fitzhardinge
2008-11-05  9:20           ` Jens Axboe
2008-11-05 10:49             ` Fernando Luis Vázquez Cao
2008-10-27  9:45     ` [PATCH 2/3] virtio_blk: set queue paravirt flag Fernando Luis Vázquez Cao
2008-10-27  9:45     ` [PATCH 3/3] xen-blkfront: " Fernando Luis Vázquez Cao
2008-10-27  9:43   ` [PATCH] virtio_blk: use noop elevator by default Fernando Luis Vázquez Cao

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=20080826143900.GM20055@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=fernando@oss.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox