From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mark Watts <m.watts@eris.qinetiq.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Innovision EIO DM-8301H/R SATA cards...
Date: 08 Aug 2003 18:20:08 +0100 [thread overview]
Message-ID: <1060363207.4937.56.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <200308081511.28238.m.watts@eris.qinetiq.com>
On Gwe, 2003-08-08 at 15:11, Mark Watts wrote:
> 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
In -ac pretty much everything "just works". Just finishing off one or
two last issues
prev parent reply other threads:[~2003-08-08 17:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 13:08 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
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 [this message]
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=1060363207.4937.56.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®