From: Dave <dave.jiang@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Brad Campbell <brad@wasp.net.au>,
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 10:34:06 -0700 [thread overview]
Message-ID: <8746466a04082610346b07ea11@mail.gmail.com> (raw)
In-Reply-To: <412E1D3E.2050307@pobox.com>
On Thu, 26 Aug 2004 13:26:22 -0400, Jeff Garzik <jgarzik@pobox.com> wrote:
> Brad Campbell wrote:
> > In which case, these drives need to be knocked back to UDMA66 to
> > function properly on anything later than 2.6.6. Don't know why.
> > I have tried multiple drives (I have 5 of them), multiple cables (lots
> > of those) and multiple bridge boards (I have 6 of those). There is no
> > combination that is reliable on the VIA controller with any transfer
> > larger than about 0x80 sectors *OR* speeds greater than UDMA66 *OR*
> > Kernel 2.6.6 or prior.
>
> We could always eliminate lba48 max-sectors increase on VIA controllers...
>
> Jeff
>
>
Has Brad tried it with native SATA drives instead of bridges? Could be
VIA controllers incompatible with PATA->SATA bridges.....
--
-= 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.).
next prev parent reply other threads:[~2004-08-26 17:34 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 [this message]
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=8746466a04082610346b07ea11@mail.gmail.com \
--to=dave.jiang@gmail.com \
--cc=brad@wasp.net.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.