public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: phillips@bonn-fries.net
Cc: riel@conectiva.com.br, Ulrich.Weigand@de.ibm.com,
	zaitcev@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: The IBM order relaxation patch
Date: Thu, 07 Feb 2002 07:10:37 -0800 (PST)	[thread overview]
Message-ID: <20020207.071037.74749998.davem@redhat.com> (raw)
In-Reply-To: <E16Yq9D-0000bD-00@starship.berlin>
In-Reply-To: <Pine.LNX.4.33L.0202071254430.17850-100000@imladris.surriel.com> <E16Yq9D-0000bD-00@starship.berlin>

   From: Daniel Phillips <phillips@bonn-fries.net>
   Date: Thu, 7 Feb 2002 16:07:39 +0100
   
   I'd rather see rmap go in in its simplest possible form, outperforming the
   current virtual scanning method on basic page replacement performance, rather 
   that using the other things we know rmap can do as the argument for inclusion.
   It's for this reason that I'm concentrating on the fork speedup.

Ok, but just keep in mind that failing for < 3 order page allocations
would be a regression from what is in there now.

  reply	other threads:[~2002-02-07 15:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-06 21:50 The IBM order relaxation patch Ulrich Weigand
2002-02-07  0:18 ` Alan Cox
2002-02-07  4:01   ` David S. Miller
2002-02-07 12:16     ` Rik van Riel
2002-02-07 12:29       ` David S. Miller
2002-02-07 12:42         ` Rik van Riel
2002-02-07 12:58         ` Hugh Dickins
2002-02-07 14:12 ` Daniel Phillips
2002-02-07 14:55   ` Rik van Riel
2002-02-07 15:07     ` Daniel Phillips
2002-02-07 15:10       ` David S. Miller [this message]
2002-02-09 20:21   ` Alex Bligh - linux-kernel
  -- strict thread matches above, loose matches on Subject: below --
2002-02-07 15:05 Ulrich Weigand
2002-02-07 15:13 ` Rik van Riel
2002-02-07 17:57 ` Daniel Phillips
2002-02-06 19:13 Pete Zaitcev

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=20020207.071037.74749998.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.net \
    --cc=riel@conectiva.com.br \
    --cc=zaitcev@redhat.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