From: "Stephen C. Tweedie" <sct@redhat.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Mike Galbraith <mikeg@wen-online.de>,
"Stephen C. Tweedie" <sct@redhat.com>,
Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC][PATCH] Re: Linux 2.4.4-ac10
Date: Mon, 21 May 2001 14:36:04 +0100 [thread overview]
Message-ID: <20010521143604.C8080@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0105200703270.5531-100000@imladris.rielhome.conectiva>; from riel@conectiva.com.br on Sun, May 20, 2001 at 07:04:31AM -0300
Hi,
On Sun, May 20, 2001 at 07:04:31AM -0300, Rik van Riel wrote:
> On Sun, 20 May 2001, Mike Galbraith wrote:
> >
> > Looking at the locking and trying to think SMP (grunt) though, I
> > don't like the thought of taking two locks for each page until
>
> > 100%. The data in that block is toast anyway. A big hairy SMP
> > box has to feel reclaim_page(). (they probably feel the zone lock
> > too.. probably would like to allocate blocks)
>
> Indeed, but this is a separate problem. Doing per-CPU private
> (small, 8-32 page?) free lists is probably a good idea
Ingo already implemented that for Tux2.
Cheers,
Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-05-21 13:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0105181403280.5531-100000@imladris.rielhome.conectiva>
[not found] ` <Pine.LNX.4.33.0105181936240.583-100000@mikeg.weiden.de>
2001-05-18 18:19 ` Ingo Oeser
2001-05-18 18:23 ` Rik van Riel
2001-05-18 18:58 ` Ingo Oeser
2001-05-18 20:12 ` Rik van Riel
2001-05-18 20:24 ` Mike Galbraith
2001-05-18 20:09 ` Mike Galbraith
2001-05-18 22:44 ` Rik van Riel
2001-05-18 22:58 ` Stephen C. Tweedie
2001-05-19 2:12 ` Rik van Riel
2001-05-19 2:32 ` Mike Castle
2001-05-19 6:45 ` Mike Galbraith
2001-05-19 4:40 ` Mike Galbraith
2001-05-19 17:13 ` [RFC][PATCH] " Mike Galbraith
2001-05-19 21:41 ` Rik van Riel
2001-05-20 3:29 ` Mike Galbraith
2001-05-20 6:42 ` Rik van Riel
2001-05-20 8:08 ` Mike Galbraith
[not found] ` <Pine.LNX.4.21.0105200546241.5531-100000@imladris.rielhome.conectiva>
2001-05-20 9:47 ` Mike Galbraith
[not found] ` <Pine.LNX.4.21.0105200703270.5531-100000@imladris.rielhome.conectiva>
2001-05-21 13:36 ` Stephen C. Tweedie [this message]
2001-05-20 21:54 ` Pavel Machek
2001-05-21 20:32 ` David Weinehall
2001-05-23 15:34 ` Rik van Riel
2001-05-23 17:24 ` Jonathan Morton
2001-05-25 8:39 ` Pavel Machek
2001-05-23 17:51 ` Scott Anderson
2001-05-25 8:10 ` David Weinehall
2001-05-25 18:39 ` Pavel Machek
2001-06-04 19:22 ` RPM Installation - Compilation errors jalaja devi
2001-05-24 8:48 ` [RFC][PATCH] Re: Linux 2.4.4-ac10 Mike Galbraith
2001-05-24 9:10 ` Rik van Riel
2001-05-24 10:32 ` Mike Galbraith
2001-05-24 11:03 ` Rik van Riel
2001-05-24 14:23 ` Mike Galbraith
2001-05-20 15:32 ` Ingo Oeser
2001-05-20 17:38 ` Mike Galbraith
2001-05-20 13:44 ` Zlatko Calusic
2001-05-20 17:58 ` Mike Galbraith
2001-05-20 19:32 ` Marcelo Tosatti
2001-05-20 21:03 ` Marcelo Tosatti
2001-05-21 3:54 ` Mike Galbraith
[not found] <Pine.LNX.4.21.0105201837240.5531-100000@imladris.rielhome.conectiva>
2001-05-21 3:44 ` Mike Galbraith
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=20010521143604.C8080@redhat.com \
--to=sct@redhat.com \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mikeg@wen-online.de \
--cc=riel@conectiva.com.br \
/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