From: Andrea Arcangeli <andrea@suse.de>
To: Al Peat <al_kernel@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hard_sector / hard_nr_sectors
Date: Tue, 31 Oct 2000 02:08:18 +0100 [thread overview]
Message-ID: <20001031020818.A29519@athlon.random> (raw)
In-Reply-To: <20001030185639.93318.qmail@web10105.mail.yahoo.com>
In-Reply-To: <20001030185639.93318.qmail@web10105.mail.yahoo.com>; from al_kernel@yahoo.com on Mon, Oct 30, 2000 at 10:56:39AM -0800
On Mon, Oct 30, 2000 at 10:56:39AM -0800, Al Peat wrote:
> I was wondering if someone could give me a quick
> overview of the differences between sector/nr_sectors
> and hard_sector/hard_nr_sectors in blk_dev.h's request
> structure, or point me to some
> documentation/discussion on this?
The reason hard_nr_sectors is been introduced is that it allows all device
drivers to handle merged I/O requests transparently. In 2.4.x we do merging at
the highlevel layer unconditionally and so it was necessary to avoid breakage
of lowlevel drivers.
This way device drivers can limit themself to look at
current_request->buffer/current_nr_sectors/sector... and to call end_request(1)
once the I/O is completed (end_that_request_first will take care of updating
current->sector/nr_sector for the next pass of the request_fn without the need
of ugly changes to the lowlevel drivers).
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-10-31 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 18:56 hard_sector / hard_nr_sectors Al Peat
2000-10-31 1:08 ` Andrea Arcangeli [this message]
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=20001031020818.A29519@athlon.random \
--to=andrea@suse.de \
--cc=al_kernel@yahoo.com \
--cc=linux-kernel@vger.kernel.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