From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: scameron@beardog.cce.hp.com, mike.miller@hp.com, jens.axboe@oracle.com
Subject: CCISS performance drop in buffered disk reads in newer kernels
Date: Mon, 07 Dec 2009 12:45:58 +0200 [thread overview]
Message-ID: <4B1CDCE6.5040502@pardus.org.tr> (raw)
Hi,
We have 2 HP Proliant DL380G5 server running with different kernels.
I was inspecting a basic kernel-compile time. On the one with 2.6.25.20
kernel, the compilation took ~1.5 minutes. On the one with 2.6.30.9
kernel, it took ~6 minutes. Both systems are using ccache as a build helper.
Then I ran hdparm on both systems, the results are below.
I'd like to help debugging this issue through bisect or another method
but since there are more parameters that differ from one to the other
server than only the kernel version, I'm a little bit stuck.
Thanks,
Ozan
### 2.6.30.9 (Slow one, compiled with PAE support, FS is ext4) ###
# sync; sleep 2; echo 3 > /proc/sys/vm/drop_caches; hdparm -tT -vvvv
/dev/cciss/c0d0p5
/dev/cciss/c0d0p5:
HDIO_DRIVE_CMD(identify) failed: Invalid exchange
readonly = 0 (off)
readahead = 256 (on)
geometry = 245410/255/32, sectors = 2002550382, start = 4225158
Timing cached reads: 12038 in 2.00 seconds = 6027.00 MB/sec
Timing buffered disk reads: 184 MB in 3.00 seconds = 61.31
MB/sec <------ Note the drop here!
# dmesg | grep cciss
[ 0.000000] Kernel command line: root=LABEL=PARDUS_ROOT vga=791
splash=silent quiet resume=/dev/cciss/c0d0p1
[ 6.023542] cciss 0000:18:08.0: PCI INT A -> GSI 19 (level, low) ->
IRQ 19
[ 6.023566] cciss: MSI init failed
[ 6.053008] IRQ 19/cciss0: IRQF_DISABLED is not guaranteed on shared IRQs
[ 6.053015] cciss0: <0x3238> at PCI 0000:18:08.0 IRQ 19 using DAC
[ 6.053918] cciss/c0d0: p1 p2 < p5 >
[ 6.320852] kjournald2 starting: pid 190, dev cciss!c0d0p5:8, commit
interval 5 seconds
[ 6.322344] EXT4-fs: mounted filesystem cciss!c0d0p5 with ordered
data mode
[ 10.994505] EXT4 FS on cciss!c0d0p5, internal journal on cciss!c0d0p5:8
[ 11.783302] Adding 2112508k swap on /dev/cciss/c0d0p1. Priority:-1
extents:1 across:2112508k
[ 16.696090] JBD: barrier-based sync failed on cciss!c0d0p5:8 -
disabling barriers
### 2.6.25.20 (Fast one, no PAE support, FS is ext3) ###
# sync;sleep 2; echo 3 > /proc/sys/vm/drop_caches; hdparm -tT -vvv
/dev/cciss/c0d0p5
/dev/cciss/c0d0p5:
readonly = 0 (off)
readahead = 256 (on)
geometry = 245426/255/32, sectors = 2002678902, start = 4096638
Timing cached reads: 10650 MB in 2.00 seconds = 5334.38 MB/sec
Timing buffered disk reads: 420 MB in 3.01 seconds = 139.72 MB/sec
# dmesg | grep cciss
Kernel command line: root=LABEL=PARDUS_ROOT vga=791 splash=silent quiet
resume=/dev/cciss/c0d0p1
cciss0: <0x3238> at PCI 0000:18:08.0 IRQ 212 using DAC
cciss/c0d0: p1 p2 < p5 >
EXT3 FS on cciss/c0d0p5, internal journal
Adding 2048248k swap on /dev/cciss/c0d0p1. Priority:-1 extents:1
across:2048248k
next reply other threads:[~2009-12-07 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 10:45 Ozan Çağlayan [this message]
2009-12-07 16:32 ` CCISS performance drop in buffered disk reads in newer kernels Miller, Mike (OS Dev)
2009-12-07 18:21 ` Ozan Çağlayan
2009-12-07 18:39 ` Jens Axboe
2009-12-07 19:30 ` Miller, Mike (OS Dev)
2009-12-07 19:32 ` Jens Axboe
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=4B1CDCE6.5040502@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.miller@hp.com \
--cc=scameron@beardog.cce.hp.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