From: Hugh Dickins <hugh@veritas.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-mm@kvack.org
Subject: Re: 0-order allocation problem
Date: Thu, 16 Aug 2001 01:07:21 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.21.0108160050470.1034-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.33L.0108152036040.5646-100000@imladris.rielhome.conectiva>
On Wed, 15 Aug 2001, Rik van Riel wrote:
> On Thu, 16 Aug 2001, Hugh Dickins wrote:
>
> > 1. Why test free_shortage() in the high-order case? The caller has
> > asked for a high-order allocation, and is prepared to wait: we
> > haven't found what the caller needs yet, we certainly should not
> > wait forever, but we should try harder: it's irrelevant whether
> > there's a free shortage or not - we've found a contiguity shortage.
>
> It may be irrelevant, but remember that try_to_free_pages()
> doesn't free any pages if there is no free shortage.
I think you've caught me out there. When "try_to_free_pages()"
actually tries to free pages is something that changes from time
to time, and I hadn't looked to see what current behaviour is.
All the more reason not to call free_shortage(), if try_to_free_pages()
will make its own decision. The important bit is probably to recycle
round to page_launder(); or perhaps it's just to spend a little time
in the hope that something will turn up.... (not Linus' favoured
strategy, but currently contiguity is given no weight at all in
choosing pages).
> Besides, even if it did chances are you wouldn't be able
> to allocate that 2MB contiguous area any time next week ;)
I'll settle for less...
Hugh
--
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-16 0:07 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
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 [this message]
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.21.0108160050470.1034-100000@localhost.localdomain \
--to=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.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