From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Martin Hicks <mort@sgi.com>,
linux-mm@kvack.org, raybry@sgi.com, ak@suse.de
Subject: Re: [PATCH/RFC 0/4] VM: Manual and Automatic page cache reclaim
Date: Thu, 28 Apr 2005 21:16:22 +1000 [thread overview]
Message-ID: <4270C606.8040000@yahoo.com.au> (raw)
In-Reply-To: <20050427233335.492d0b6f.akpm@osdl.org>
Andrew Morton wrote:
> Martin Hicks <mort@sgi.com> wrote:
>
>>The patches introduce two different ways to free up page cache from a
>> node: manually through a syscall and automatically through flag
>> modifiers to a mempolicy.
>
>
> Backing up and thinking about this a bit more....
>
>
>> Currently if a job is started and there is page cache lying around on a
>> particular node then allocations will spill onto remote nodes and page
>> cache won't be reclaimed until the whole system is short on memory.
>> This can result in a signficiant performance hit for HPC applications
>> that planned on that memory being allocated locally.
>
>
> Why do it this way at all?
>
> Is it not possible to change the page allocator's zone fallback mechanism
> so that once the local node's zones' pages are all allocated, we don't
> simply advance onto the next node? Instead, could we not perform a bit of
> reclaim on this node's zones first? Only advance onto the next nodes if
> things aren't working out?
Yeah. I got a patch that does this. It is quite possible - you have
to make some balance so you don't go to shit on workloads that have
a working set larger than a single node's memory, but...
--
SUSE Labs, Novell Inc.
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-04-28 11:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 15:08 Martin Hicks
2005-04-27 17:36 ` Nikita Danilov
2005-04-28 6:33 ` Andrew Morton
2005-04-28 11:16 ` Nick Piggin [this message]
2005-04-28 11:56 ` Rik van Riel
2005-04-28 12:53 ` Martin Hicks
2005-05-03 7:17 ` Ray Bryant
2005-05-03 8:08 ` Andrew Morton
2005-05-03 13:21 ` Martin Hicks
2005-05-04 1:23 ` Andrew Morton
2005-05-12 18:53 ` Martin Hicks
2005-05-12 18:57 ` Martin Hicks
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=4270C606.8040000@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=mort@sgi.com \
--cc=raybry@sgi.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