From: Hans Reiser <reiser@namesys.com>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: Dieter N|tzel <Dieter.Nuetzel@hamburg.de>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Daniel Phillips <phillips@bonn-fries.net>,
ReiserFS List <reiserfs-list@namesys.com>,
"Gryaznova E." <grev@namesys.botik.ru>
Subject: Re: [reiserfs-list] Re: [resent PATCH] Re: very slow parallel read performance
Date: Tue, 28 Aug 2001 12:46:43 +0400 [thread overview]
Message-ID: <3B8B5A73.258A3A0E@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0108280645130.607-100000@mikeg.weiden.de>
Mike Galbraith wrote:
>
> On Tue, 28 Aug 2001, Dieter N|tzel wrote:
>
> > * readahead do not show dramatic differences
> > * killall -STOP kupdated DO
> >
> > Yes, I know it is dangerous to stop kupdated but my disk show heavy thrashing
> > (seeks like mad) since 2.4.7ac4. killall -STOP kupdated make it smooth and
> > fast, again.
>
> Interesting.
>
> A while back, I twiddled the flush logic in buffer.c a little and made
> kupdated only handle light flushing.. stay out of the way when bdflush
> is running. This and some dynamic adjustment of bdflush flushsize and
> not stopping flushing right _at_ (biggie) the trigger level produced
> very interesting improvements. (very marked reduction in system time
> for heavy IO jobs, and large improvement in file rewrite throughput)
>
> -Mike
Can you send us the patch, and Elena will run some tests on it?
Hans
next prev parent reply other threads:[~2001-08-28 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 1:08 [resent PATCH] Re: very slow parallel read performance Dieter Nützel
2001-08-28 0:05 ` Marcelo Tosatti
2001-08-28 1:54 ` Daniel Phillips
2001-08-28 5:01 ` Mike Galbraith
2001-08-28 8:46 ` Hans Reiser [this message]
2001-08-28 19:17 ` [reiserfs-list] " Mike Galbraith
2001-08-28 18:18 ` Andrew Morton
2001-08-28 18:45 ` Hans Reiser
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=3B8B5A73.258A3A0E@namesys.com \
--to=reiser@namesys.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=grev@namesys.botik.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
--cc=phillips@bonn-fries.net \
--cc=reiserfs-list@namesys.com \
/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