From: Andrew Morton <akpm@zip.com.au>
To: Alexander Moibenko <moibenko@fnal.gov>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: fsync delays for a long time.
Date: Thu, 14 Feb 2002 13:41:39 -0800 [thread overview]
Message-ID: <3C6C2F13.B8A30DB@zip.com.au> (raw)
In-Reply-To: <E16bTZO-0001DH-00@the-village.bc.nu> <Pine.SGI.4.31.0202141526080.3270649-100000@fsgi03.fnal.gov>
Alexander Moibenko wrote:
>
> On Thu, 14 Feb 2002, Alan Cox wrote:
>
> > > > > 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.
> > > >
> > > > That may amplify it but in the 2.2 case fsync on any sensible sized file
> > > > is already horribly performing. It hits databases like solid quite badly
> > > >
> > > please elaborate on "sensible sized". In my case it is less then 20MB.
> >
> > That ought to be ok. Andrew may well be right in that case.
> >
> Then what is your advise. Switch to 2.4.x?
I would recommend that, yes. One consideration: if the problem
is still appearing in 2.4 then it is about 1000 times more
likely to get fixed.
What filesystem were you using, BTW? ext2?
If you do test on 2.4, and the problem still appears, please try
wget http://www.zip.com.au/~akpm/linux/2.4/2.4.18-pre9/make_request.patch
patch -p1 < make_request.patch
next prev parent reply other threads:[~2002-02-14 21:43 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
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 [this message]
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=3C6C2F13.B8A30DB@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