From: Jens Axboe <axboe@suse.de>
To: John Bradford <john@grabjohn.com>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] take 48-bit lba a bit further
Date: Sun, 6 Apr 2003 15:32:50 +0200 [thread overview]
Message-ID: <20030406133250.GN786@suse.de> (raw)
In-Reply-To: <200304061332.h36DWnaD000165@81-2-122-30.bradfords.org.uk>
On Sun, Apr 06 2003, John Bradford wrote:
> > Thanks for taking the previous bit Alan, here's an incremental update to
> > 2.5.66-ac2. Just cleans up the 'when to use 48-bit lba' logic a bit per
> > Andries suggestion, and also expands the request size for 48-bit lba
> > capable drives to 512KiB.
> >
> > Works perfectly in testing here, ext2/3 generates nice big 512KiB
> > requests and the drive flies.
>
> Then, don't we want to be using 48-bit lba all the time on compatible devices
> instead of falling back to 28-bit when possible to save a small amount of
> instruction overhead? (Or is that what we're doing already? I haven't really
> had the time to follow this thread).
The logic in the patch is to enable large requests _if_ the drive can do
48-bit lba. However, we will only use 48-bit lba commands if the request
is either beyond 2^28 sectors _or_ bigger than 256 sectors since neither
of these can be addressed with 28-bit lba.
See rq_lba48 in the patch, it explains it.
--
Jens Axboe
next prev parent reply other threads:[~2003-04-06 13:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-06 13:07 [PATCH] take 48-bit lba a bit further Jens Axboe
2003-04-06 13:32 ` John Bradford
2003-04-06 13:32 ` Jens Axboe [this message]
2003-04-06 14:35 ` Alan Cox
2003-04-06 15:47 ` John Bradford
2003-04-06 15:59 ` Jens Axboe
2003-04-06 16:04 ` Jens Axboe
2003-04-06 16:08 ` John Bradford
2003-04-06 16:43 ` Petr Vandrovec
2003-04-06 16:27 ` Alan Cox
2003-04-07 7:50 ` Jens Axboe
[not found] <175955253@toto.iv>
2003-04-06 23:04 ` Peter Chubb
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=20030406133250.GN786@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=john@grabjohn.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