public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: Konstantin Sobolev <kos@supportwizard.com>
Cc: Justin Cormack <justin@street-vision.com>,
	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 16:52:04 +0200	[thread overview]
Message-ID: <407EA194.20904@gmx.de> (raw)
In-Reply-To: <200404151848.05857.kos@supportwizard.com>

Konstantin Sobolev wrote:
> On Thursday 15 April 2004 18:33, Justin Cormack wrote:
> 
>>On Thu, 2004-04-15 at 15:26, Konstantin Sobolev wrote:
>>
>>>On Thursday 15 April 2004 18:00, Justin Cormack wrote:
>>>
>>>>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...
>>>
>>>Attached are files for 2.6.5-mm5 with highmem, ACPI and APIC turned off.
>>
>>ah. Make a filesystem on it and mount it and try again. I see you have
>>no partition table and so probably no filesystem. This means the block
>>size is set to default 512byte not 4k which makes disk operations slow.
>>Any filesystem should default to block size of 4k, eg ext2.
> 
> 
> Very interesting!
> created partition table,
> kos sata # mkfs.ext2 /dev/sda1
> [..skipped..]
> kos mnt # cd /
> kos / # mkdir wd
> kos / # mount /dev/sda1 /wd
> kos / # hdparm -t -a8192 /dev/sda

[snip]

> So first time it gave the same loosy 27 MB/s and subsequent tests give pretty 
> good 68 MB/s! Why?

I once reported that to lkml but got no reaction. siimage.c doesn't show 
this behaviour.

Prakash

  reply	other threads:[~2004-04-15 14:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14 22:36 poor sata performance on 2.6 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
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 [this message]
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=407EA194.20904@gmx.de \
    --to=prakashkc@gmx.de \
    --cc=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