From: Jens Axboe <axboe@suse.de>
To: Jeff Garzik <jeff@garzik.org>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Tejun Heo <htejun@gmail.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Mark Lord <liml@rtr.ca>, Hannes Reinecke <hare@suse.de>
Subject: Re: jgarzik and max-sectors: out of memory
Date: Tue, 30 May 2006 11:10:02 +0200 [thread overview]
Message-ID: <20060530091002.GG4199@suse.de> (raw)
In-Reply-To: <20060530090258.GA17478@havoc.gtf.org>
On Tue, May 30 2006, Jeff Garzik wrote:
> On Tue, May 30, 2006 at 10:36:29AM +0200, Jens Axboe wrote:
> > On Tue, May 30 2006, Jeff Garzik wrote:
> > > Jens Axboe wrote:
> > > >Yep lets please do that, I don't think libata ever had any problems with
> > > >256 sectors other than perhaps a worry that it would break "something" :-)
> > >
> > > There were definite bugs in the past with 256 (versus <= 255) sectors...
> >
> > Hardware or software? IIRC, the hardware ones were largely an urban
> > legend.
>
> Software.
>
> Alan is submitting a couple PATA drivers limited to 255 though...
And I'm sure some are even lower than that. Of course libata should be
be imposing anything on the driver, the logic that drivers/ide uses for
this is actually pretty sane:
if (device_lba28)
max_hw_sectors = 256;
if (device_lba48)
max_hw_sectors = 65536;
if (max_sectors > more_than_controller_supports)
max_sectors = more_than_controller_supports;
or something close to that.
--
Jens Axboe
next prev parent reply other threads:[~2006-05-30 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 19:37 jgarzik and max-sectors: out of memory Jeff Garzik
2006-05-27 19:49 ` Mark Lord
2006-05-27 20:02 ` Jeff Garzik
2006-05-27 20:43 ` Jens Axboe
2006-05-30 4:58 ` Jeff Garzik
2006-05-30 8:36 ` Jens Axboe
2006-05-30 9:02 ` Jeff Garzik
2006-05-30 9:10 ` Jens Axboe [this message]
2006-05-30 9:15 ` Jeff Garzik
2006-05-30 9:25 ` 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=20060530091002.GG4199@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hare@suse.de \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).