From: Jeff Garzik <jeff@garzik.org>
To: Jens Axboe <axboe@suse.de>
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 00:58:37 -0400 [thread overview]
Message-ID: <447BD0FD.1000200@garzik.org> (raw)
In-Reply-To: <200605272243.41832.axboe@suse.de>
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...
Jeff
next prev parent reply other threads:[~2006-05-30 4:58 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 [this message]
2006-05-30 8:36 ` Jens Axboe
2006-05-30 9:02 ` Jeff Garzik
2006-05-30 9:10 ` Jens Axboe
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=447BD0FD.1000200@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=hare@suse.de \
--cc=htejun@gmail.com \
--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).