From: Linus Torvalds <torvalds@transmeta.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Ben LaHaise <bcrl@redhat.com>,
Daniel Phillips <phillips@bonn-fries.net>,
linux-mm@kvack.org
Subject: Re: [RFC][DATA] re "ongoing vm suckage"
Date: Tue, 7 Aug 2001 13:50:52 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0108071232001.1031-100000@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0108071621180.1439-100000@duckman.distro.conectiva>
On Tue, 7 Aug 2001, Rik van Riel wrote:
>
> Hmmmm, indeed. All lazy movement can do is make it
> easier to run into a wall, but it should still be
> possible without it ...
Yes.
One of the things this problem seems to show is that "kswapd" really does
too many different things.
Some people who wake up kswapd really want kswapd to work at _freeing_
pages. Exactly because things like network traffic, buffer flushing etc
may not be able to do everything due to atomicity constraints or fear of
deadlocks.
At the same time, kswapd _also_ ends up doing background aging, so kswapd
basically wakes up itself once a second. And when kswapd wakes up itself
it does _not_ want to actively free pages, so it has to have that test for
"free_shortage()"..
Linus
--
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-mm.org/
next prev parent reply other threads:[~2001-08-07 20:50 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-03 23:44 Ben LaHaise
2001-08-04 1:29 ` Rik van Riel
2001-08-04 3:06 ` Daniel Phillips
2001-08-04 3:13 ` Linus Torvalds
2001-08-04 3:23 ` Rik van Riel
2001-08-04 3:35 ` Linus Torvalds
2001-08-04 3:26 ` Ben LaHaise
2001-08-04 3:34 ` Rik van Riel
2001-08-04 3:38 ` Linus Torvalds
2001-08-04 3:48 ` Linus Torvalds
2001-08-04 4:14 ` Ben LaHaise
2001-08-04 4:20 ` Linus Torvalds
2001-08-04 4:39 ` Ben LaHaise
2001-08-04 4:47 ` Linus Torvalds
2001-08-04 5:13 ` Ben LaHaise
2001-08-04 5:28 ` Linus Torvalds
2001-08-04 6:37 ` Linus Torvalds
2001-08-04 5:38 ` Marcelo Tosatti
2001-08-04 7:13 ` Rik van Riel
2001-08-04 23:28 ` [PATCH] Unlazy activate (was: re "ongoing vm suckage") Daniel Phillips
2001-08-04 14:22 ` [RFC][DATA] re "ongoing vm suckage" Mike Black
2001-08-04 17:08 ` Linus Torvalds
2001-08-04 20:54 ` Jonathan Morton
2001-08-05 4:19 ` Michael Rothwell
2001-08-05 18:40 ` Marcelo Tosatti
2001-08-05 20:20 ` Linus Torvalds
2001-08-06 20:32 ` Rob Landley
2001-08-05 15:24 ` Mike Black
2001-08-05 20:04 ` Linus Torvalds
2001-08-05 20:23 ` Alan Cox
2001-08-05 20:33 ` Linus Torvalds
2001-08-04 16:21 ` Mark Hemment
2001-08-07 15:45 ` Ben LaHaise
2001-08-07 16:22 ` Linus Torvalds
2001-08-07 16:51 ` Ben LaHaise
2001-08-07 17:08 ` Linus Torvalds
2001-08-07 18:17 ` Andrew Morton
2001-08-07 18:40 ` Ben LaHaise
2001-08-07 21:33 ` Daniel Phillips
2001-08-07 21:33 ` Linus Torvalds
2001-08-07 17:04 ` Linus Torvalds
2001-08-07 17:11 ` Rik van Riel
2001-08-07 19:12 ` Linus Torvalds
2001-08-07 19:21 ` Rik van Riel
2001-08-07 20:50 ` Linus Torvalds [this message]
2001-08-07 23:36 ` Linus Torvalds
2001-08-07 17:26 ` Chris Mason
2001-08-07 18:13 ` Daniel Phillips
2001-08-07 18:40 ` Chris Mason
2001-08-07 19:52 ` Linus Torvalds
2001-08-07 20:22 ` Chris Mason
2001-08-08 1:08 ` Theodore Tso
2001-08-08 1:13 ` Linus Torvalds
2001-08-08 2:25 ` Marcelo Tosatti
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=Pine.LNX.4.33.0108071232001.1031-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=bcrl@redhat.com \
--cc=linux-mm@kvack.org \
--cc=phillips@bonn-fries.net \
--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