linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Dave <dave.jiang@gmail.com>,
	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 21:50:17 +0400	[thread overview]
Message-ID: <412E22D9.2060000@wasp.net.au> (raw)
In-Reply-To: <412E2190.7030504@pobox.com>

Jeff Garzik wrote:
> Dave wrote:
> 
>> On Thu, 26 Aug 2004 13:26:22 -0400, Jeff Garzik <jgarzik@pobox.com> 
>> wrote:
>>
>>> We could always eliminate lba48 max-sectors increase on VIA 
>>> controllers...
> 
> 
>> Has Brad tried it with native SATA drives instead of bridges? Could be
>> VIA controllers incompatible with PATA->SATA bridges.....
> 
> 
> 
> Oh wait.  That's a damned good point.
> 
> I wonder if there is a problem with LBA48 large transfers (>256 sectors) 
> and bridges.  Is Brad definitely using a bridge?  I may have missed that 
> detail in a flurry of emails :)

Yep.. using a bridge!
How to detect the bridge though?

  reply	other threads:[~2004-08-26 17:50 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
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 [this message]
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=412E22D9.2060000@wasp.net.au \
    --to=brad@wasp.net.au \
    --cc=dave.jiang@gmail.com \
    --cc=jgarzik@pobox.com \
    --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).