From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: "Adam Kropelin" <akropel1@rochester.rr.com>
Cc: Andrea Arcangeli <andrea@suse.de>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Rik spreading bullshit about VM
Date: Wed, 16 Jan 2002 22:49:49 +0100 [thread overview]
Message-ID: <20020116215003Z287940-13996+7210@vger.kernel.org> (raw)
Adam Kropelin wrote:
> Andrea Arcangeli wrote:
> <snip>
> >I don't have a single bugreport about the current 2.4.18pre2aa2 VM (except
> >perhaps the bdflush wakeup that seems to be a little too late and that
> >deals to lower numbers with slow write load etc.., fixable with bdflush
> >tuning).
>
> I don't know if this is a reference to the issue I reported under the
> "Writeout in recent kernels..." thread or not. If not, my apologies for
> clogging up this new "discussion".
>
> As reported[0] in the above-mentioned thread, the bdflush tuning parameters
> you suggested made no difference in my test case other than slightly
> adjusting the temporal relationship between writeout and file transfer. -aa
> still performs slightly worse than both 2.4.17 stock and -rmap. 2.4.13-ac7
> currently beats all competitors.
Put Andrew's read-latency.patch on -aa (10_vm-22) and see what you get out of
it. It should fly...
-Dieter
--
Dieter Nützel
Graduate Student, Computer Science
University of Hamburg
Department of Computer Science
@home: Dieter.Nuetzel@hamburg.de
next reply other threads:[~2002-01-16 21:50 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 21:49 Dieter Nützel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-17 4:01 Rik spreading bullshit about VM rwhron
2002-01-17 1:26 rwhron
2002-01-17 19:08 ` bill davidsen
2002-01-17 19:49 ` Rik van Riel
2002-01-17 20:22 ` Dan Chen
2002-01-17 1:16 Andrea Scrimieri
2002-01-17 0:08 V-man
2002-01-17 0:31 ` Rik van Riel
2002-01-17 7:44 ` Luigi Genoni
2002-01-17 11:11 ` Rik van Riel
2002-01-17 15:25 ` John Jasen
[not found] <Pine.LNX.4.33L.0201162235480.32617-100000@imladris.surriel .com>
2002-01-16 19:04 ` Andrea Arcangeli
2002-01-16 20:11 ` Jose Luis Domingo Lopez
2002-01-16 20:58 ` Richard Gooch
2002-01-16 21:10 ` Dave Jones
2002-01-16 21:17 ` Rik van Riel
2002-01-17 0:20 ` Luigi Genoni
2002-01-16 21:17 ` Craig Knox
2002-01-16 20:58 ` Bongani Hlope
2002-01-16 20:55 ` John Levon
2002-01-16 21:21 ` Bongani Hlope
2002-01-16 21:29 ` Adam Kropelin
2002-01-16 21:58 ` Diego Calleja
2002-01-16 22:02 ` Rik van Riel
2002-01-16 21:59 ` Diego Calleja
2002-01-16 22:44 ` Chris Chabot
2002-01-17 8:18 ` Christoph Rohland
2002-01-17 0:07 ` Erik Mouw
2002-01-17 0:25 ` J Sloan
2002-01-17 1:15 ` Erik Mouw
2002-01-17 17:40 ` bill davidsen
2002-01-17 14:14 ` Alan Cox
2002-01-18 4:30 ` Bosko Radivojevic
2002-01-17 0:38 ` Rik van Riel
2002-01-17 1:50 ` Nicolas Pitre
2002-01-17 11:45 ` Rik van Riel
2002-01-17 12:02 ` Stephan von Krawczynski
2002-01-17 2:14 ` Andrea Scrimieri
2002-01-17 12:07 ` Rik van Riel
2002-01-17 13:11 ` Andrea Scrimieri
2002-01-17 13:15 ` Rik van Riel
2002-01-17 14:02 ` Alan Cox
2002-01-17 21:41 ` Trever L. Adams
2002-01-18 1:46 ` brian
2002-01-17 1:52 ` Stephen Satchell
2002-01-17 13:26 ` Alan Cox
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=20020116215003Z287940-13996+7210@vger.kernel.org \
--to=dieter.nuetzel@hamburg.de \
--cc=akropel1@rochester.rr.com \
--cc=andrea@suse.de \
--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