From: Lee Revell <rlrevell@joe-job.com>
To: William Thompson <wt@electro-mechanical.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SATA in 2.6.17 vs 2.6.15 (x86/ICH6)
Date: Fri, 30 Jun 2006 17:04:00 -0400 [thread overview]
Message-ID: <1151701440.32444.44.camel@mindpipe> (raw)
In-Reply-To: <20060630184156.GA8086@electro-mechanical.com>
On Fri, 2006-06-30 at 14:41 -0400, William Thompson wrote:
> *** I'm not on the list, please always keep me in CC ***
>
> The speed of SATA in 2.6.17 is significantly lower in my test than 2.6.15.
>
> In .15, I would see over 10mb/sec avg writing over 16,000 files (~2.4gb) to a
> fat32 partition.
>
> In .17, I see it start at 2-3mb/sec and work it's way down to 500kb/sec
> towards the end. Even the system is not as responsive (The system's / is a
> tmpfs which all programs, including /usr, are stored), not even when using
> ssh.
>
> I used the same .config in .17 as I did with .15 (make oldconfig)
What does the oprofile output look like for both cases?
Lee
next prev parent reply other threads:[~2006-06-30 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 18:41 SATA in 2.6.17 vs 2.6.15 (x86/ICH6) William Thompson
2006-06-30 21:04 ` Lee Revell [this message]
2006-07-06 18:56 ` William Thompson
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=1151701440.32444.44.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wt@electro-mechanical.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