linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Sat, 27 May 2006 22:43:41 +0200	[thread overview]
Message-ID: <200605272243.41832.axboe@suse.de> (raw)
In-Reply-To: <4478AA6C.5070305@garzik.org>

On Saturday 27 May 2006 21:37, Jeff Garzik wrote:
> ATA_MAX_SECTORS is 200, rather than than 256 like it should be.  I seem
> to recall that this was due to libata being incomplete in some area, but
> I've tried in vain for a year to remember where the alleged
> incompleteness was, to no avail.  So, my brain is out of memory :)
>
> Further -- someone with a long ATA memory correct me -- I think that we
> can increase ATA_MAX_PRD beyond 256.  Most DMA engines should just keep
> chugging along, provided that we continue to respect the 64k IDE DMA
> boundaries.

The PRD count is much less of a problem.

> So, I propose that we rename ATA_MAX_SECTORS to ATA_LBA28_SECTORS, and
> change its value to 256, and see what happens.  People have reported
> that that worked for them, so let's subject it to a wide test.  If
> people are extremely paranoid, we could increase it to 255, and then in
> the next kernel version, bump it from 255 to 256.
>
> Then we can look at increasing ATA_MAX_PRD, if that's feasible for PATA
> hardware.

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" :-)

Jens

  parent reply	other threads:[~2006-05-27 20:45 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 [this message]
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
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=200605272243.41832.axboe@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).