From: Jens Axboe <axboe@suse.de>
To: Christoph Hellwig <hch@caldera.de>,
Mark Peloquin <peloquin@us.ibm.com>,
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 10:02:30 +0100 [thread overview]
Message-ID: <20011113100230.A15827@suse.de> (raw)
In-Reply-To: <OF9F38B076.0F9781F3-ON85256B02.006D5DFE@raleigh.ibm.com> <20011112212735.A28486@caldera.de>
In-Reply-To: <20011112212735.A28486@caldera.de>
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.
--
Jens Axboe
next prev parent reply other threads:[~2001-11-13 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 20:05 Re: Hardsector size support in 2.4 and 2.5 Mark Peloquin
2001-11-12 20:27 ` [Evms-devel] " Christoph Hellwig
2001-11-13 9:02 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-13 14:24 Mark Peloquin
2001-11-13 14:39 ` 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=20011113100230.A15827@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