All of lore.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,
	jeremy@xensource.com
Subject: Re: [PATCH 1/3] block: add queue flag for paravirt frontend drivers
Date: Mon, 27 Oct 2008 13:56:24 +0100	[thread overview]
Message-ID: <20081027125624.GA22217@kernel.dk> (raw)
In-Reply-To: <1225100686.7370.79.camel@sebastian.kern.oss.ntt.co.jp>

On Mon, Oct 27 2008, Fernando Luis Vázquez Cao wrote:
> As is the case with SSD devices, we do not want to idle in AS/CFQ when
> the block device is a paravirt front-end driver. This patch adds a flag
> (QUEUE_FLAG_VIRT) which should be used by front-end drivers such as
> virtio_blk and xen-blkfront to indicate a paravirtualized device.

All three patches look fine, although we could just reuse
QUEUE_FLAG_NONROT directly. But I agree it makes sense to make the
distinction, so I've just applied 1-3.

-- 
Jens Axboe


  reply	other threads:[~2008-10-27 12:57 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
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 [this message]
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=20081027125624.GA22217@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=fernando@oss.ntt.co.jp \
    --cc=jeremy@xensource.com \
    --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 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.