linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave <dave.jiang@gmail.com>
To: Brad Campbell <brad@wasp.net.au>
Cc: linux-ide@vger.kernel.org,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	RAID Linux <linux-raid@vger.kernel.org>
Subject: Re: max_sectors in libata when using md
Date: Thu, 26 Aug 2004 08:52:48 -0700	[thread overview]
Message-ID: <8746466a0408260852205a7842@mail.gmail.com> (raw)
In-Reply-To: <412DFFA9.8030504@wasp.net.au>

On Thu, 26 Aug 2004 19:20:09 +0400, Brad Campbell <brad@wasp.net.au> wrote:
> G'day all,
> 
> Hot on the trail of this libata oddity.
> 
> 
> ATA_MAX_SECTORS == 200.
> 
> Should then the scsi layer be able to do this and queue 1/2 a Meg in a single request?
> 
> Am I looking at something completely weird? Is the block layer doing something I should know about?
> Can SATA transfers handle 1024 sectors in one go? Will Batman make it out of the cave alive?

That is decimal 200, not hex 200. Technically with ATA (or SATA)
drives you can bump it to 0x100 (256). That is the limitation of LBA28
drives. With LBA48 drives you can do 0xffff (64k) sectors per request
I believe. I wish the SATA layer would allow a mechanism to auto
detect drive being LBA48 or LBA28 and adjust accordingly instead of
just default to a very low sector count.

-- 
-= Dave =-

Software Engineer - Advanced Development Engineering Team 
Storage Component Division - Intel Corp. 
mailto://dave-DOT-jiang-AT-intel-DOT-com 
----
The views expressed in this email are
mine alone and do not necessarily 
reflect the views of my employer
(Intel Corp.).

  reply	other threads:[~2004-08-26 15:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 15:20 max_sectors in libata when using md Brad Campbell
2004-08-26 15:52 ` Dave [this message]
2004-08-26 16:30   ` Jeff Garzik
2004-08-26 16:44     ` Brad Campbell
2004-08-26 17:26       ` Jeff Garzik
2004-08-26 17:34         ` Dave
2004-08-26 17:44           ` Jeff Garzik
2004-08-26 17:50             ` Brad Campbell
2004-08-26 17:54               ` Jeff Garzik
2004-08-26 18:34                 ` Brad Campbell
2004-08-26 17:37         ` Brad Campbell
2004-08-26 16:37   ` Brad Campbell
2004-08-26 17:51     ` Jeff Garzik

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=8746466a0408260852205a7842@mail.gmail.com \
    --to=dave.jiang@gmail.com \
    --cc=brad@wasp.net.au \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-scsi@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).