linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: linux-ide@vger.kernel.org
Subject: something is dramatically wrong with buffered read performance in 2.6.32.9
Date: Wed, 17 Mar 2010 17:33:49 -0500	[thread overview]
Message-ID: <4BA158CD.6060402@hardwarefreak.com> (raw)

I recently upgraded from kernel 2.6.31.1 to 2.6.32.9.  Upon kicking the
tires on the new kernel I discovered that my two data partitions are
suffering a ~30MB/s performance loss compared to my root partition.  That's
a loss of nearly half the performance of my disk.

The root partition is a primary, formatted with EXT2.  The two data
partitions are logicals within an extended partition, both formatted with
XFS.  hdparm O_DIRECT tests show identical throughput for all 3 partitions.
 Going through the buffer cache, however, shows a huge performance drop for
the two logical partitions.  Throughput is nearly cut in half through the
buffer cache:

/dev/sda2:
 Timing O_DIRECT disk reads:  238 MB in  3.02 seconds =  78.79 MB/sec
/dev/sda2:
 Timing buffered disk reads:  208 MB in  3.00 seconds =  69.26 MB/sec

/dev/sda6:
 Timing O_DIRECT disk reads:  236 MB in  3.02 seconds =  78.14 MB/sec
/dev/sda6:
 Timing buffered disk reads:  126 MB in  3.01 seconds =  41.79 MB/sec

/dev/sda7:
 Timing O_DIRECT disk reads:  238 MB in  3.00 seconds =  79.27 MB/sec
/dev/sda7:
 Timing buffered disk reads:  126 MB in  3.03 seconds =  41.65 MB/sec

Any ideas what I'm running into here?  Did I somehow fubar something in
menuconfig?

I get the same results with dd copy tests through the buffer cache to
/dev/null.  Any idea what's wrong?  Is this a known bug?

-- 
Stan

                 reply	other threads:[~2010-03-17 22:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4BA158CD.6060402@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).