From: Jason Lunz <lunz@falooley.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Strange write starvation on 2.6.17 (and other) kernels
Date: Tue, 15 Aug 2006 18:40:41 +0000 (UTC) [thread overview]
Message-ID: <ebt4f9$sri$1@sea.gmane.org> (raw)
In-Reply-To: 44E0A69C.5030103@agh.edu.pl
szymans@agh.edu.pl said:
> I've encountered a strange problem - if an application is sequentially
> writing a large file on a busy machine, a single write() of 64KB may
> take even 30 seconds. But if I do fsync() after each write() the maximum
If the sleeps are that long, and reproducible, then maybe you can find
the offending wait by using sysrq-t while the writer is blocked.
Jason
next prev parent reply other threads:[~2006-08-15 18:41 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 [this message]
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
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='ebt4f9$sri$1@sea.gmane.org' \
--to=lunz@falooley.org \
--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