From: Tino Keitel <tino.keitel@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Strage buffer behaviour
Date: Sun, 11 Nov 2007 19:33:35 +0100 [thread overview]
Message-ID: <20071111183334.GA6770@dose.home.local> (raw)
Hi folks,
I noticed that the kernel (2.6.23.1) seems to buffer only certain
partitions on my system:
$ for i in 1 2 3 4 ; do for j in 1 2 ; do dd if=/dev/sda$i of=/dev/null
bs=1024k count=100 ; done ; done
100+0 records in
100+0 records out
104857600 bytes (105 MB) copied, 3.01471 seconds, 34.8 MB/s
100+0 records in
100+0 records out
104857600 bytes (105 MB) copied, 2.86945 seconds, 36.5 MB/s
100+0 records in
100+0 records out
104857600 bytes (105 MB) copied, 2.92038 seconds, 35.9 MB/s
100+0 records in
100+0 records out
104857600 bytes (105 MB) copied, 3.00272 seconds, 34.9 MB/s
100+0 records in
100+0 records out
104857600 bytes (105 MB) copied, 4.07722 seconds, 25.7 MB/s
100+0 records in
100+0 records out
104857600 bytes (105 MB) copied, 0.0944248 seconds, 1.1 GB/s
100+0 records in
100+0 records out
104857600 bytes (105 MB) copied, 5.61527 seconds, 18.7 MB/s
100+0 records in
100+0 records out
104857600 bytes (105 MB) copied, 0.331822 seconds, 316 MB/s
The dd command reads 100 MB from each partition two times in a row. It
looks like sda1 and sda2 are not bufferd (the first 4 dd runs), but
sda3 and sda4 are (the last 4 dd runs).
The computer is a Mac mini with a 2,5" SATA hard disk. The first 2
partitions contain EFI and MacOS X, and are unused in Linux. The last 2
partitions are an ext3 partition for / and an LVM for the rest of the
sytem.
Any hints how the dd/buffering behaviour could be explained? The system
was mostly idle, and the numbers are reproducible across reboots.
Regards,
Tino
next reply other threads:[~2007-11-11 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 18:33 Tino Keitel [this message]
2007-11-11 19:39 ` Strage buffer behaviour Heikki Orsila
2007-11-12 19:44 ` Denys Vlasenko
2007-11-12 20:46 ` Heikki Orsila
-- strict thread matches above, loose matches on Subject: below --
2007-11-14 11:02 Tomasz Chmielewski
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=20071111183334.GA6770@dose.home.local \
--to=tino.keitel@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.