From: Andrzej Szymanski <szymans@agh.edu.pl>
To: Neil Brown <neilb@suse.de>
Cc: Miquel van Smoorenburg <miquels@cistron.nl>,
linux-kernel@vger.kernel.org
Subject: Re: Strange write starvation on 2.6.17 (and other) kernels
Date: Mon, 21 Aug 2006 14:40:32 +0200 [thread overview]
Message-ID: <44E9A9C0.6000405@agh.edu.pl> (raw)
In-Reply-To: <17641.3304.948174.971955@cse.unsw.edu.au>
Neil Brown wrote:
> On Thursday August 17, miquels@cistron.nl wrote:
>
> Can you report the contents of /proc/meminfo before, during, and after
> the long pause?
> I'm particularly interested in MemTotal, Dirty, and Writeback, but the
> others are of interest too.
>
> Thanks,
> NeilBrown
I've prepared two logs, from different machines, the first one is on
software RAID5 (4 ATA disks) with deadline scheduler, the second on a
single ATA disk with CFQ scheduler. In the first case 10 writer threads
are sufficient to give large delays, in the second case I've run an
additional tar thread reading from the disk.
The logs are here:
http://galaxy.agh.edu.pl/~szymans/logs/
Each writer starts with:
Writing 200 MB to stdout without fsync
than reports each write() that lasts > 3s along with pid:
6582 - Delayed 4806 ms.
And finishes with:
Max write delay: 14968 ms.
Andrzej.
next prev parent reply other threads:[~2006-08-21 12:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 16:36 Strange write starvation on 2.6.17 (and other) kernels Andrzej Szymanski
2006-08-14 18:46 ` Jeff V. Merkey
2006-08-14 23:28 ` Grant Coady
2006-08-15 7:50 ` Andrew Morton
2006-08-15 7:51 ` Andrew Morton
2006-08-15 12:40 ` Grzegorz Kulewski
2006-08-15 14:04 ` Andrew Morton
2006-08-15 18:40 ` Jason Lunz
2006-08-16 20:54 ` Andrzej Szymanski
2006-08-17 8:36 ` Miquel van Smoorenburg
2006-08-21 1:31 ` Neil Brown
2006-08-21 12:40 ` Andrzej Szymanski [this message]
2006-08-22 7:40 ` Neil Brown
2006-08-25 5:41 ` Neil Brown
2006-08-25 8:46 ` Andrzej Szymanski
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=44E9A9C0.6000405@agh.edu.pl \
--to=szymans@agh.edu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
--cc=neilb@suse.de \
/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