From: Linus Torvalds <torvalds@transmeta.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Hugh Dickins <hugh@veritas.com>, linux-mm@kvack.org
Subject: Re: 0-order allocation problem
Date: Wed, 15 Aug 2001 15:30:02 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0108151528180.887-100000@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0108151747570.26574-100000@freak.distro.conectiva>
On Wed, 15 Aug 2001, Marcelo Tosatti wrote:
>
> __GFP_IO is not going to help us that much on anon intensive workloads
> (eg swapoff). Remember we are _never_ going to block on buffer_head's of
> on flight swap pages because we can't see them in page_launder(). (if a
> page is locked, we simply skip it)
Note that that is what we have the page_alloc (and buffer head) reserves
for - and it doesn't take that much to get the ball rolling. Certainly not
even close to our low-water-marks.. And once it snowballs it _does_ help
that people call page_launder().
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-15 22:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0108152049100.973-100000@localhost.localdomain>
2001-08-15 20:45 ` Linus Torvalds
2001-08-15 20:55 ` Marcelo Tosatti
2001-08-15 22:30 ` Linus Torvalds [this message]
2001-08-15 22:34 ` Rik van Riel
2001-08-15 23:27 ` Hugh Dickins
2001-08-15 22:15 ` Marcelo Tosatti
2001-08-15 22:00 ` Rik van Riel
2001-08-15 22:15 ` Rik van Riel
2001-08-15 23:09 ` Hugh Dickins
2001-08-15 21:54 ` Marcelo Tosatti
2001-08-15 23:38 ` Rik van Riel
2001-08-16 0:07 ` Hugh Dickins
2001-08-15 22:44 ` Marcelo Tosatti
2001-08-16 0:50 ` Linus Torvalds
2001-08-16 8:30 ` Daniel Phillips
2001-08-16 10:26 ` Stephen C. Tweedie
2001-08-16 12:18 ` Daniel Phillips
2001-08-16 15:35 ` Eric W. Biederman
2001-08-16 16:37 ` Stephen C. Tweedie
2001-08-17 3:20 ` Eric W. Biederman
2001-08-17 11:45 ` Stephen C. Tweedie
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.0108151528180.887-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=marcelo@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