Linux LVM users
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Joe Thornber <joe@fib011235813.fsnet.co.uk>
Cc: Andrew Morton <akpm@zip.com.au>,
	Neil Brown <neilb@cse.unsw.edu.au>,
	linux-lvm@sistina.com, linux-kernel@vger.kernel.org
Subject: Re: [linux-lvm] LVM2 modifies the buffer_head struct?
Date: Thu Jul  4 04:00:02 2002	[thread overview]
Message-ID: <20020704090010.GB6204@suse.de> (raw)
In-Reply-To: <20020704085735.GA1175@fib011235813.fsnet.co.uk>

On Thu, Jul 04 2002, Joe Thornber wrote:
> On Thu, Jul 04, 2002 at 10:39:41AM +0200, Jens Axboe wrote:
> > Which just means that device mapper needs to do the stacking properly,
> > EOD.
> 
> You don't think it does it properly ATM ?

Well as I said, it's in the grey zone. If you look at stacking from a
submission and end_io point of view, then yes it works. Anywhere in
between, no it doesn't.

See my previous mails in this thread :-)

-- 
Jens Axboe

  reply	other threads:[~2002-07-04  4:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-02  8:41 [linux-lvm] LVM2 modifies the buffer_head struct? Tom Walcott
2002-07-02  9:17 ` Joe Thornber
2002-07-03  5:09   ` Jens Axboe
2002-07-03  5:23     ` Andrew Morton
2002-07-03  7:01     ` Joe Thornber
2002-07-03  7:10       ` Jens Axboe
2002-07-03 23:44         ` Neil Brown
2002-07-04  0:39           ` Andrew Morton
2002-07-04  2:46           ` Joe Thornber
2002-07-04  2:58           ` Jens Axboe
2002-07-04  3:34             ` Andrew Morton
2002-07-04  3:40               ` Jens Axboe
2002-07-04  3:58                 ` Joe Thornber
2002-07-04  4:00                   ` Jens Axboe [this message]
2002-07-04  4:38                 ` Andrew Morton
2002-07-07 14:52                   ` Joe Thornber
  -- strict thread matches above, loose matches on Subject: below --
2002-07-05  0:21 Mark Peloquin

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=20020704090010.GB6204@suse.de \
    --to=axboe@suse.de \
    --cc=akpm@zip.com.au \
    --cc=joe@fib011235813.fsnet.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-lvm@sistina.com \
    --cc=neilb@cse.unsw.edu.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