public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: will <whansard@sbcglobal.net>
To: linux-kernel@vger.kernel.org
Subject: disk speed regression kernel 2.6.29 and after
Date: Wed, 23 Sep 2009 07:08:58 -0500	[thread overview]
Message-ID: <4ABA0FDA.9090707@sbcglobal.net> (raw)

I had been using an old 2.6.22 kernel on my machine, and I often backup one partition 
of my main hard drive to a partition on a second hard drive. The main hard drive is 
sata 640 gigs, and the second is a pata 320 gig. copying this partition from one 
drive to the other with dd takes about 3 minutes and 30 seconds. When I installed 
kernel 2.6.30, and 2.6.31, the time took 9 minutes and 20 seconds. I decided to go to 
the trouble of compiling all the kernels between, and kernels 2.6.22-2.6.28 all do 
the operation in about 3 minutes and 30 seconds. 2.6.29- newer all take about 9 
minutes and 20 seconds. The partition is 16 gigs. each drive seems to be as fast as 
before otherwise, it's just much slower copying from one drive to another, which I do 
very often. This is an nforce 3 based motherboard, amd southbridge, i think, with 4 
gigs of ram, athlon 64x2. 32 bit kernel. has anyone heard of this problem?
I currently have 3  hard drives hooked up.
a 200 gig on a promise controller,
a 320 gig on the amd pata?
a 640 sata on the nv i think.
The motherboard is a Asrock-AM2NF3-VSTA
copying this partition with dd or cat or schily's dd between any of these 3
different hard drives takes different times depending on the speed of the drive with
kernels 2.6.22-2.6.28, but takes about 9 minutes and 30 seconds on any of the drives
with the kernels 2.6.29 and after.
Please cc me with any followups or anything. thanks.

             reply	other threads:[~2009-09-23 12:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23 12:08 will [this message]
2009-09-23 12:23 ` disk speed regression kernel 2.6.29 and after Jon Smirl
2009-09-24  3:06   ` Will
2009-09-24  9:10     ` Arjan van de Ven
2009-09-24  3:07 ` Robert Hancock
2009-09-24  4:35   ` Will
2009-09-24  7:44     ` odie
2009-09-24  9:01       ` Will
2009-09-24 10:41       ` Will
2009-09-24 12:26       ` Bartlomiej Zolnierkiewicz
2009-09-24 16:26         ` Will
2009-09-24 17:34           ` Bartlomiej Zolnierkiewicz
2009-09-24 18:11             ` Frans Pop
2009-09-24 19:12               ` Bartlomiej Zolnierkiewicz
2009-09-24 21:50                 ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2009-09-24 21:34 Andrew Randrianasulu

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=4ABA0FDA.9090707@sbcglobal.net \
    --to=whansard@sbcglobal.net \
    --cc=linux-kernel@vger.kernel.org \
    /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