public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Mark Peloquin <peloquin@us.ibm.com>
Cc: Christoph Hellwig <hch@caldera.de>,
	dalecki@evision.ag, linux-kernel@vger.kernel.org,
	evms-devel@lists.sourceforge.net
Subject: Re: [Evms-devel] Re: Re: Hardsector size support in 2.4 and 2.5
Date: Tue, 13 Nov 2001 15:39:00 +0100	[thread overview]
Message-ID: <20011113153900.A17933@suse.de> (raw)
In-Reply-To: <OF2769A354.FD887DD7-ON85256B03.004C650C@raleigh.ibm.com>
In-Reply-To: <OF2769A354.FD887DD7-ON85256B03.004C650C@raleigh.ibm.com>

On Tue, Nov 13 2001, Mark Peloquin wrote:
> On Tue, Nov 13 2001, Jens Axboe wrote:
> > On Mon, Nov 12 2001, Christoph Hellwig wrote:
> > > On Mon, Nov 12, 2001 at 02:05:19PM -0600, Mark Peloquin wrote:
> > > > So any block device, can always expect to receive buffer heads
> > > > whose b_rsector value represents the offset from the beginning
> > > > of that device in 512 byte multiples? And this will continue
> > > > to hold true in 2.5 as well?
> > >
> > > There is a good chance that no 2.5 block driver will ever see a
> buffer_head,
> > > take a look at
> http://www.kernel.org/pub/linux/kernel/people/axboe/v2.5/ for
> > > details.
> 
> > To expand on the specific point -- in 2.5, what will change is that
> > b_rsector (or equiv field, bi_sector in bio) will be offset from the
> > beginning of the disk, not the beginning of the partition. This moves
> > toe partion remaps out of the driver itself.
> 
> This is an important difference, so I'd like to make sure I fully
> understand the scope. Ok, so bi_sector for partitions will be
> disk relative, not partition relative. I'll assume that bi_sector

Well, know you have b_rdev == MKDEV(3, 5) and b_rsector = 0 for the
first sector of /dev/hda5 -- with the new remapped approach, this would
be b_rdev = MKDEV(3, 0) b_rsector 123456 (imagined value, of course).

> will be set inside of submit_bh. So top level block devices always
> see something that is disk relative. Is this change ONLY for
> partitions? And if not, how will this affect what top and

Inside generic_make_request currentl, so stacking works.

> intermediate levels of stacked block devices receive for a
> bi_sector value? If I had MD on LVM on partitions, what would
> bi_sector value initially be relative to? The MD device, the
> LVM device, or the disk underlying the partitions? It seems it

Nothing changes for stacking. The only difference is that the remapping
for partition offset is now done above the driver. Drivers can still
remap b_rdev and b_rsector as they see fit.

-- 
Jens Axboe


  reply	other threads:[~2001-11-13 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 14:24 [Evms-devel] Re: Re: Hardsector size support in 2.4 and 2.5 Mark Peloquin
2001-11-13 14:39 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-12 20:05 Mark Peloquin
2001-11-12 20:27 ` [Evms-devel] " Christoph Hellwig
2001-11-13  9:02   ` Jens Axboe

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=20011113153900.A17933@suse.de \
    --to=axboe@suse.de \
    --cc=dalecki@evision.ag \
    --cc=evms-devel@lists.sourceforge.net \
    --cc=hch@caldera.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peloquin@us.ibm.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