From: Justin Cormack <justin@street-vision.com>
To: Konstantin Sobolev <kos@supportwizard.com>
Cc: Ryan Geoffrey Bourgeois <rgb005@latech.edu>,
Kernel mailing list <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: poor sata performance on 2.6
Date: Thu, 15 Apr 2004 15:00:32 +0100 [thread overview]
Message-ID: <1082037632.19567.72.camel@lotte.street-vision.com> (raw)
In-Reply-To: <200404151734.03786.kos@supportwizard.com>
hmm, odd. I get 50MB/s or so from normal (7200, 8MB cache) WD disks, and
Seagate from the same controller. Can you send lspci, /proc/interrupts
and dmesg...
Justin
On Thu, 2004-04-15 at 14:34, Konstantin Sobolev wrote:
> On Thursday 15 April 2004 16:02, Justin Cormack wrote:
> > Ah I see from your config you have himem_4G turned on. How much memory
> > do you have? Sii3112 appears (I dont actually have datasheets) to only
> > have 32 bit DMA support, and will use bounce buffers quite a lot of the
> > time if you turn on himem at all, reducing throughput substantially. Try
> > again with no himem support at all and see if it helps.
>
> I have 1.5 GB. I tried to disable highmem, now less than 1GB is visible, but
> there is no noticable difference in SATA performance:
>
> siimage:
> /dev/hde:
> setting fs readahead to 8129
> setting 32-bit IO_support flag to 1
> setting multcount to 16
> multcount = 16 (on)
> IO_support = 1 (32-bit)
> unmaskirq = 0 (off)
> using_dma = 1 (on)
> keepsettings = 0 (off)
> readonly = 0 (off)
> readahead = 8128 (on)
> geometry = 16383/255/63, sectors = 145226112, start = 0
> Timing buffer-cache reads: 1428 MB in 2.00 seconds = 713.75 MB/sec
> Timing buffered disk reads: 100 MB in 3.03 seconds = 32.99 MB/sec
>
> libata
> /dev/sda:
> setting fs readahead to 8192
> readahead = 8192 (on)
> Timing buffered disk reads: 82 MB in 3.02 seconds = 27.17 MB/sec
next prev parent reply other threads:[~2004-04-15 14:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 22:36 Konstantin Sobolev
2004-04-15 3:54 ` Ryan Geoffrey Bourgeois
2004-04-15 10:55 ` Konstantin Sobolev
2004-04-15 12:02 ` Justin Cormack
2004-04-15 13:34 ` Konstantin Sobolev
2004-04-15 14:00 ` Justin Cormack [this message]
2004-04-15 14:26 ` Konstantin Sobolev
2004-04-15 14:33 ` Justin Cormack
2004-04-15 14:48 ` Konstantin Sobolev
2004-04-15 14:52 ` Prakash K. Cheemplavam
2004-04-15 17:30 ` Denis Vlasenko
2004-04-16 1:05 ` Jeff Garzik
2004-04-16 14:48 ` Denis Vlasenko
2004-04-16 16:59 ` Konstantin Sobolev
2004-04-16 17:46 ` cira
2004-04-20 12:41 ` Prakash K. Cheemplavam
2004-04-15 15:51 ` Ryan Geoffrey Bourgeois
2004-04-15 23:34 ` Simon Koch
2004-04-16 0:11 ` poor sata performance on 2.6 - Promise SX4 Ryan Geoffrey Bourgeois
2004-04-16 1:03 ` poor sata performance on 2.6 Jeff Garzik
2004-04-19 16:45 ` Henrik Gustafsson
2004-04-19 16:56 ` Jeff Garzik
2004-04-15 7:12 ` Lenar Lõhmus
2004-04-15 10:40 ` Konstantin Sobolev
2004-04-15 12:37 ` Denis Vlasenko
2004-04-15 12:57 ` Lenar Lõhmus
2004-04-15 16:54 ` Denis Vlasenko
2004-04-15 13:05 ` Konstantin Sobolev
2004-04-15 19:50 ` Pavel Machek
2004-04-15 21:13 ` Konstantin Sobolev
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=1082037632.19567.72.camel@lotte.street-vision.com \
--to=justin@street-vision.com \
--cc=kos@supportwizard.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rgb005@latech.edu \
/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®