virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	xen-devel <xen-devel@lists.xensource.com>,
	virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: More virtio users
Date: Mon, 11 Jun 2007 08:41:09 +0200	[thread overview]
Message-ID: <20070611064107.GA7341@kernel.dk> (raw)
In-Reply-To: <1181479060.16428.37.camel@localhost.localdomain>

On Sun, Jun 10 2007, Rusty Russell wrote:
> On Sun, 2007-06-10 at 11:16 +0300, Avi Kivity wrote:
> > Rusty Russell wrote:
> > > Lguest doesn't have a framebuffer, so maybe this is a good thing for me
> > > to hack on, but I promised myself I'd finish NAPI for the net device,
> > > and tag for block device first.
> > >   
> > 
> > If you're touching the block device, passing a request's io priority to 
> > the host can be useful.
> 
> OK, here's the interdiff.  I still don't handle non-fs requests, but I
> haven't seen any yet.  I should probably BUG_ON() there and wait for
> Jens to scream...

Ehm no, that would certainly cause screaming :-)

Checking for blk_fs_request() and terminating the request if you don't
know how to handle it is the correct thing to do, a BUG() would
definitely not be.

Patch looks good to me, though:

> +	blk_queue_prep_rq(vblk->disk->queue, blk_queue_start_tag);
> +

is quite a novel way, I actually had to look that code up to check
whether it was correct. I'd much prefer a little wrapper around that,
ala:

static int virtio_block_prep(request_queue_t *q, struct request *rq)
{
        if (!blk_queue_start_tag(q, rq))
                return BLKPREP_OK;

        return BLKPREP_DEFER;
}

That is much easier to read, and as a bonus it wont eat your request
just because you run out of tags! The fact that blk_queue_start_tag()
just happens to share the prep_rq_fn definition is by coincidence only.

-- 
Jens Axboe

  parent reply	other threads:[~2007-06-11  6:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <466BA965.6050208@qumranet.com>
2007-06-10  8:06 ` [Xen-devel] More virtio users Muli Ben-Yehuda
     [not found] ` <20070610080602.GD3738@rhun.haifa.ibm.com>
2007-06-10  8:09   ` Avi Kivity
     [not found]   ` <466BB1AF.1000601@qumranet.com>
2007-06-12 22:07     ` [kvm-devel] " Arnd Bergmann
2007-06-12 23:40       ` Caitlin Bestler
2007-06-10  8:13 ` Rusty Russell
2007-06-11  3:04 ` [Xen-devel] " ron minnich
     [not found] ` <1181463220.16428.24.camel@localhost.localdomain>
2007-06-10  8:16   ` Avi Kivity
     [not found]   ` <466BB34B.9050105@qumranet.com>
2007-06-10 12:37     ` Rusty Russell
     [not found]     ` <1181479060.16428.37.camel@localhost.localdomain>
2007-06-11  6:41       ` Jens Axboe [this message]
2007-06-11  7:29         ` Rusty Russell
     [not found]         ` <1181546953.16428.96.camel@localhost.localdomain>
2007-06-11  7:33           ` Jens Axboe
2007-06-12  0:31             ` Rusty Russell
     [not found]             ` <1181608287.16428.127.camel@localhost.localdomain>
2007-06-12  6:24               ` Jens Axboe
2007-06-12  7:52                 ` Rusty Russell
     [not found]                 ` <1181634747.6237.79.camel@localhost.localdomain>
2007-06-12  7:56                   ` Jens Axboe
2007-06-11  8:16   ` [Xen-devel] " Gerd Hoffmann
2007-06-11  8:19     ` Avi Kivity
2007-06-11 19:24     ` Anthony Liguori
2007-06-11 23:19     ` Rusty Russell
2007-06-12  3:36       ` Anthony Liguori
     [not found]       ` <466E14A6.6020400@codemonkey.ws>
2007-06-12  4:07         ` Benjamin Herrenschmidt
     [not found]     ` <1181603983.16428.100.camel@localhost.localdomain>
2007-06-12  0:47       ` Benjamin Herrenschmidt
2007-06-12 22:01 ` [kvm-devel] " Arnd Bergmann
2007-06-14 16:27   ` [Xen-devel] " Mark Williamson
2007-06-10  7:33 Avi Kivity

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=20070611064107.GA7341@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=rusty@rustcorp.com.au \
    --cc=virtualization@lists.linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).