public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: Rik van Riel <riel@conectiva.com.br>
Cc: rwhron@earthlink.net, linux-kernel@vger.kernel.org
Subject: Re: 2.4.18pre4aa1
Date: Fri, 25 Jan 2002 06:18:01 +0100	[thread overview]
Message-ID: <20020125061801.W1735@khan.acc.umu.se> (raw)
In-Reply-To: <20020124235608.C1096@earthlink.net> <Pine.LNX.4.33L.0201250256170.32617-100000@imladris.surriel.com>
In-Reply-To: <Pine.LNX.4.33L.0201250256170.32617-100000@imladris.surriel.com>; from riel@conectiva.com.br on Fri, Jan 25, 2002 at 02:57:02AM -0200

On Fri, Jan 25, 2002 at 02:57:02AM -0200, Rik van Riel wrote:
> On Thu, 24 Jan 2002 rwhron@earthlink.net wrote:
> 
> > > workloads, I'm not sure I want to make the system more
> > > unfair just to better accomodate dbench ;)
> >
> > I'm wondering if rmap is a little too aggressive on
> > read-ahead, and if that has a negative impact on
> > a complex workload.
> 
> I haven't changed the readahead code one bit compared
> to 2.4 mainline, but I'm wondering the same.
> 
> Fixing readahead window sizing has been on my TODO list
> for quite a while already.

One thing that struck me about this; doesn't both the rmap-patches and
the aa-patches contain other changes than merely changes to the VM? If
so, couldn't these changes tip the result in an unfair direction?! After
all, what we want is a VM-to-VM shoot-out, not a VM-to-VM+whatever
shoot-out. After all, one would assume that the non VM-related changes
would be merged to the kernel no matter what VM is used, right?

Then again, maybe I just ate the blue pill and returned to a world of
illusions not knowing what's best for me.


Regards: David Weinehall
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Maintainer of the v2.0 kernel   //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

  reply	other threads:[~2002-01-25  5:18 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-24  5:23 2.4.18pre4aa1 rwhron
2002-01-24  6:27 ` 2.4.18pre4aa1 Daniel Phillips
2002-01-25  0:09   ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-28  9:53     ` 2.4.18pre4aa1 Daniel Phillips
2002-01-28 15:29       ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-28 20:28         ` 2.4.18pre4aa1 Daniel Phillips
2002-01-28 23:40           ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-29  0:15             ` 2.4.18pre4aa1 Daniel Phillips
2002-01-29 13:05               ` 2.4.18pre4aa1 Pavel Machek
2002-01-25  0:19   ` 2.4.18pre4aa1 rwhron
2002-01-25  0:29     ` 2.4.18pre4aa1 Rik van Riel
2002-01-25  3:23       ` 2.4.18pre4aa1 rwhron
2002-01-25  3:35         ` 2.4.18pre4aa1 Rik van Riel
2002-01-25  4:56           ` 2.4.18pre4aa1 rwhron
2002-01-25  4:57             ` 2.4.18pre4aa1 Rik van Riel
2002-01-25  5:18               ` David Weinehall [this message]
2002-01-25 17:03                 ` 2.4.18pre4aa1 Rik van Riel
2002-01-25 17:29                   ` 2.4.18pre4aa1 Dave Jones
2002-01-25 12:26           ` 2.4.18pre4aa1 Dave Jones
2002-01-25 14:57             ` 2.4.18pre4aa1 rwhron
2002-01-28  0:37         ` 2.4.18pre4aa1 Andrea Arcangeli
2002-01-25  0:11 ` 2.4.18pre4aa1 Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2002-01-22  6:48 2.4.18pre4aa1 Andrea Arcangeli
2002-01-22  6:58 ` 2.4.18pre4aa1 Robert Love
2002-01-22  7:37   ` 2.4.18pre4aa1 Dan Chen
2002-01-22  7:43     ` 2.4.18pre4aa1 Robert Love
2002-01-22 10:02     ` 2.4.18pre4aa1 Russell King
2002-01-22 10:12       ` 2.4.18pre4aa1 Robert Love

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=20020125061801.W1735@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=rwhron@earthlink.net \
    /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