From: Andrew Morton <akpm@zip.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alexander Moibenko <moibenko@fnal.gov>, linux-kernel@vger.kernel.org
Subject: Re: fsync delays for a long time.
Date: Thu, 14 Feb 2002 12:51:14 -0800 [thread overview]
Message-ID: <3C6C2342.5044B738@zip.com.au> (raw)
In-Reply-To: <Pine.SGI.4.31.0202140951330.3076325-100000@fsgi03.fnal.gov> from "Alexander Moibenko" at Feb 14, 2002 10:03:57 AM <E16bPqi-0000c5-00@the-village.bc.nu>
Alan Cox wrote:
>
> > run my gdbm application and bonnie test on the same device.
> > When gdbm comes to the point when it calls fsync it delays for a long
> > time.
>
> fsync on a very large file is very slow on the 2.2 kernels
This could very well be due to request allocation starvation.
fsync is sleeping in __get_request_wait() while bonnie keeps
on stealing all the requests.
Recall that patch you dropped on Tuesday? :)
> > result. IDE is even worse in our case. In the discussion it was also said
> > that fsync for 2.4.x is modified. But does it fix a problem?
>
> 2.4 is a lot smarter about flushing only the things it needs to. That
> makes it dependant on the number of blocks to write not some embarrasingly
> large power of the file size
OBTW: It seems that fsync_inode_data_buffers() will livelock if
another process is writing to the same file. gargh.
-
next prev parent reply other threads:[~2002-02-14 20:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 16:03 fsync delays for a long time Alexander Moibenko
2002-02-14 17:39 ` Alan Cox
2002-02-14 20:51 ` Andrew Morton [this message]
2002-02-14 21:09 ` Alan Cox
2002-02-14 21:12 ` Alexander Moibenko
2002-02-14 21:37 ` Alan Cox
2002-02-14 21:26 ` Alexander Moibenko
2002-02-14 21:41 ` Andrew Morton
2002-02-14 22:18 ` Alexander Moibenko
2002-02-14 21:20 ` Andrew Morton
2002-02-14 21:38 ` Alan Cox
2002-02-15 16:48 ` Stephen C. Tweedie
2002-02-15 17:24 ` Simon Kirby
2002-02-15 19:07 ` Andrew Morton
2002-02-15 19:21 ` Simon Kirby
2002-02-17 12:47 ` Bill Davidsen
2002-02-17 16:45 ` Simon Kirby
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=3C6C2342.5044B738@zip.com.au \
--to=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=moibenko@fnal.gov \
/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