From: "Stephen C. Tweedie" <sct@redhat.com>
To: riel@nl.linux.org
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Simon Kirby <sim@stormix.com>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
Andrea Arcangeli <andrea@suse.de>,
linux-mm@kvack.org, Ben LaHaise <bcrl@redhat.com>,
linux-kernel@vger.rutgers.edu
Subject: Re: [PATCH] 2.3.99-pre6-3+ VM rebalancing
Date: Wed, 26 Apr 2000 13:29:15 +0100 [thread overview]
Message-ID: <20000426132915.J3792@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0004260814130.16202-100000@duckman.conectiva>; from riel@conectiva.com.br on Wed, Apr 26, 2000 at 08:15:14AM -0300
Hi,
On Wed, Apr 26, 2000 at 08:15:14AM -0300, Rik van Riel wrote:
> On Wed, 26 Apr 2000, Stephen C. Tweedie wrote:
> > On Tue, Apr 25, 2000 at 12:06:58PM -0700, Simon Kirby wrote:
> > >
> > > Sorry, I made a mistake there while writing..I was going to give an
> > > example and wrote 60 seconds, but I didn't actually mean to limit
> > > anything to 60 seconds. I just meant to make a really big global lru
> > > that contains everything including page cache and swap. :)
> >
> > Doesn't work. If you do that, a "find / | grep ..." swaps out
> > everything in your entire system.
> >
> > Getting the VM to respond properly in a way which doesn't freak out
> > in the mass-filescan case is non-trivial. Simple LRU over all pages
> > simply doesn't cut it.
>
> It seems to work pretty well, because pages "belonging to" processes
> are mapped into the address space of each process and will never go
> through swap_out() if shrink_mmap() will succeed.
I know. The post wasn't talking about what we do now. It was talking
about a hypothetical LRU which covers "everything including page cache
and swap." LRU over just the page cache pages works fine. If you
start treating swap exactly the same, on a page-by-page LRU, then a
filesystem "find" scan will swap out most of your VM. Bad news.
--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:[~2000-04-26 12:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-23 2:08 Rik van Riel
2000-04-25 1:25 ` Simon Kirby
2000-04-25 15:09 ` Rik van Riel
2000-04-25 15:59 ` Andrea Arcangeli
2000-04-25 17:20 ` Rik van Riel
2000-04-25 18:36 ` Simon Kirby
2000-04-25 18:59 ` Jeff Garzik
2000-04-25 19:06 ` Simon Kirby
2000-04-25 19:34 ` Rik van Riel
2000-04-26 11:01 ` Stephen C. Tweedie
2000-04-26 11:15 ` Rik van Riel
2000-04-26 12:29 ` Stephen C. Tweedie [this message]
2000-04-26 12:45 ` David S. Miller
2000-04-26 11:25 ` David S. Miller
2000-04-26 13:00 ` Stephen C. Tweedie
2000-04-26 13:11 ` David S. Miller
2000-04-26 15:23 ` Stephen C. Tweedie
2000-04-26 15:25 ` David S. Miller
2000-04-26 16:09 ` Stephen C. Tweedie
2000-04-27 20:28 ` Simon Kirby
2000-04-27 22:32 ` Jamie Lokier
2000-04-26 13:46 ` Rik van Riel
2000-04-26 14:33 ` David S. Miller
2000-04-26 16:31 ` Andi Kleen
2000-04-26 15:28 ` David S. Miller
2000-04-26 15:41 ` Andi Kleen
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=20000426132915.J3792@redhat.com \
--to=sct@redhat.com \
--cc=andrea@suse.de \
--cc=bcrl@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=riel@nl.linux.org \
--cc=sim@stormix.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