From: Ingo Molnar <mingo@elte.hu>
To: Rik van Riel <riel@conectiva.com.br>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-mm@kvack.org
Subject: Re: [patch] VM stable again?
Date: Mon, 15 May 2000 21:30:50 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.10.10005152122580.8896-100000@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.21.0005151608590.20410-100000@duckman.distro.conectiva>
On Mon, 15 May 2000, Rik van Riel wrote:
> I've thought about this but it doesn't seem worth the extra complexity
> to me. Just making sure that while our task is freeing pages nobody
> else will grab those pages without having also freed some pages seems
> to be enough to me.
actually wouldnt it be simpler to always call try_to_free_pages() when the
zone is low on memory? This will keep the pressure on the system to
recover from the low memory situation, and it reuses the low_on_memory
flag. The new free_before_allocate flag is a 'now we are really low on
memory' flag.
> Furthermore, the "SMP locality" you talk about will probably be
> completely overshadowed by the non-locality of the VM freeing code
> anyway...
But it would be a performance optimization for sure, a __free_pages() +
__alloc_pages() is saved - this can make a big difference if (a mostly
clean) pagecache is shrunk.
Ingo
--
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-05-15 19:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-15 15:12 Rik van Riel
2000-05-15 15:31 ` Ingo Molnar
2000-05-15 15:27 ` Rik van Riel
2000-05-15 16:15 ` Ingo Molnar
2000-05-15 18:36 ` Linus Torvalds
2000-05-15 18:29 ` Linus Torvalds
2000-05-15 19:01 ` Stephen C. Tweedie
2000-05-15 19:10 ` Rik van Riel
2000-05-15 19:30 ` Ingo Molnar [this message]
2000-05-15 19:27 ` Rik van Riel
2000-05-15 19:22 ` Ingo Molnar
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.10.10005152122580.8896-100000@elte.hu \
--to=mingo@elte.hu \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=sct@redhat.com \
--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