From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Joe Korty <joe.korty@ccur.com>,
Andreas Dilger <adilger@clusterfs.com>,
rusty@rustcorp.com.au, riel@conectiva.com.br,
linux-kernel@vger.kernel.org, hch@sgi.com,
Stephen Tweedie <sct@redhat.com>
Subject: Re: 2.4.21-pre2 stalls out when running unixbench
Date: 06 Jan 2003 13:23:55 +0000 [thread overview]
Message-ID: <1041859435.2691.51.camel@sisko.scot.redhat.com> (raw)
In-Reply-To: <3E19739F.84C57EFC@digeo.com>
Hi,
On Mon, 2003-01-06 at 12:16, Andrew Morton wrote:
> Well personally I prefer slow-and-safe. But we could make 2.4
> do what 2.5 is doing - one pass through the superblocks to start
> the syncs and a second pass to wait on them all.
The 2.5 approach has the problem that it can start queuing writeback for
multiple fs'es on the same disk at the same time --- I wouldn't be
surprised if it increases thrashing in that case. But I guess I'm not
too concerned about sync() performance itself, as long as the in-kernel
background writeback is being done sensibly.
> This is fragile stuff though....
Yep.
--Stephen
next prev parent reply other threads:[~2003-01-06 13:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 16:56 Joe Korty
2003-01-03 20:07 ` Andrew Morton
2003-01-03 20:30 ` Andrew Morton
2003-01-04 1:11 ` Joe Korty
2003-01-04 11:11 ` Andrew Morton
2003-01-05 2:58 ` Joe Korty
2003-01-06 12:10 ` Stephen C. Tweedie
2003-01-06 12:15 ` John Bradford
2003-01-06 13:20 ` Stephen C. Tweedie
2003-01-06 12:16 ` Andrew Morton
2003-01-06 13:23 ` Stephen C. Tweedie [this message]
2003-01-11 8:10 ` Christoph Hellwig
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=1041859435.2691.51.camel@sisko.scot.redhat.com \
--to=sct@redhat.com \
--cc=adilger@clusterfs.com \
--cc=akpm@digeo.com \
--cc=hch@sgi.com \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®