public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
	virtualization <virtualization@lists.linux-foundation.org>,
	Andi Kleen <ak@muc.de>,
	jens.axboe@oracle.com
Subject: Re: PATCH 7/8] lguest: the block driver
Date: Wed, 11 Apr 2007 14:00:24 +1000	[thread overview]
Message-ID: <1176264024.26372.93.camel@localhost.localdomain> (raw)
In-Reply-To: <84144f020704100436y3405f104x8345c72556d961e9@mail.gmail.com>

On Tue, 2007-04-10 at 14:36 +0300, Pekka Enberg wrote:
> On 4/10/07, Rusty Russell <rusty@rustcorp.com.au> wrote:
> > > +/* Jens gave me this nice helper to end all chunks of a request. */
> > > +static void end_entire_request(struct request *req, int uptodate)
> > > +{
> > > +       if (end_that_request_first(req, uptodate, req->hard_nr_sectors))
> > > +               BUG();
> > > +       add_disk_randomness(req->rq_disk);
> > > +       blkdev_dequeue_request(req);
> > > +       end_that_request_last(req, uptodate);
> > > +}
> 
> On 4/10/07, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> > Perhaps we should move this to generic code (i.e. block/ll_rw_blk.c)?

Yeah, Jens said to put it in here and he'd hoist it later.

> Uhm, I am bit confused now. Why don't you just use end_request() here?

What a question!  end_request() doesn't end a request!  What a crazy
idea!

As far as I can tell, every name in the block layer is actually some
variant of "fuck off, this is too complicated for you to understand".

Hope that clarifies!
Rusty.


  reply	other threads:[~2007-04-11  4:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 11:04 [PATCH 0/8] lguest Rusty Russell
2007-04-10 11:05 ` [PATCH 1/8] lguest: the guest code Rusty Russell
2007-04-10 11:06   ` [PATCH 2/8] lguest: the host code Rusty Russell
2007-04-10 11:07     ` [PATCH 3/8] lguest: the asm offsets Rusty Russell
2007-04-10 11:08       ` [PATCH 4/8] lguest: the Makefile and Kconfig Rusty Russell
2007-04-10 11:08         ` [PATCH 5/8] lguest: the console driver Rusty Russell
2007-04-10 11:09           ` [PATCH 5/8] lguest: the net driver Rusty Russell
2007-04-10 11:11           ` [PATCH 6/8] " Rusty Russell
2007-04-10 11:12             ` PATCH 7/8] lguest: the block driver Rusty Russell
2007-04-10 11:12               ` [PATCH 8/8] lguest: the documentation, example launcher Rusty Russell
2007-04-10 11:28               ` PATCH 7/8] lguest: the block driver Pekka Enberg
2007-04-10 11:36                 ` Pekka Enberg
2007-04-11  4:00                   ` Rusty Russell [this message]
2007-04-11  5:29                     ` Pekka Enberg

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=1176264024.26372.93.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=ak@muc.de \
    --cc=akpm@linux-foundation.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=virtualization@lists.linux-foundation.org \
    /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