From: Justin Cormack <justin@street-vision.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Mark Watts <m.watts@eris.qinetiq.com>,
Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Innovision EIO DM-8301H/R SATA cards...
Date: 08 Aug 2003 16:16:12 +0100 [thread overview]
Message-ID: <1060355773.28644.8.camel@lotte> (raw)
In-Reply-To: <3F33B3B9.7030905@pobox.com>
On Fri, 2003-08-08 at 15:29, Jeff Garzik wrote:
> Mark Watts wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> >
> >
> >>Mark Watts wrote:
> >>
> >>>-----BEGIN PGP SIGNED MESSAGE-----
> >>>Hash: SHA1
> >>>
> >>>
> >>>My local supplier has started doing some SATA cards....
> >>>
> >>>http://www.ivmm.com/eio/products_sata_pci_host.html
> >>>
> >>>
> >>>The chip on the board i the screenshot looks vaguely like a Silicon Image
> >>>chip - - am I correct in thinking that these are supported in linux?
> >>
> >>If they are Silicon Image, yes, they are supported.
> >
> >
> > Great stuff - can someone confirm whether I still need to do the folloing for
> > the latest 2.4.22 kernels in order to get good performance?
> >
> > # hdparm -d1 -X66 /dev/hdX
> > # echo "max_kb_per_request:15" > /proc/.ide/hdX/settings
>
>
> I have no idea :( I'm off in libata land, which will soon support
> Silicon Image SATA as well...
the answer is yes - there hasnt been an update to the driver. Andre
Hedrick says he has fixed it a month or so ago but has not released it
yet.
btw echo "max_kb_per_request:15" > /proc/.ide/hdX/settings is not for
good performance (it may halve your performance on some drives) it is a
bug workaround.
Look forward to testing libata on Silicon Image.
Justin
next prev parent reply other threads:[~2003-08-08 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 13:08 Innovision EIO DM-8301H/R SATA cards Mark Watts
2003-08-08 13:21 ` Jeff Garzik
2003-08-08 14:11 ` Mark Watts
2003-08-08 14:29 ` Jeff Garzik
2003-08-08 15:16 ` Justin Cormack [this message]
2003-08-08 17:21 ` Alan Cox
2003-08-11 7:51 ` Mark Watts
2003-08-11 8:57 ` Christian Reichert
2003-08-11 12:39 ` Jeff Garzik
2003-08-08 17:20 ` Alan Cox
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=1060355773.28644.8.camel@lotte \
--to=justin@street-vision.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.watts@eris.qinetiq.com \
/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.