From: Martin Hicks <mort@sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>, Linux MM <linux-mm@kvack.org>,
Andrew Morton <akpm@osdl.org>,
torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] VM: add vm.free_node_memory sysctl
Date: Wed, 3 Aug 2005 10:24:40 -0400 [thread overview]
Message-ID: <20050803142440.GQ26803@localhost> (raw)
In-Reply-To: <20050803141529.GX10895@wotan.suse.de>
On Wed, Aug 03, 2005 at 04:15:29PM +0200, Andi Kleen wrote:
> On Wed, Aug 03, 2005 at 09:56:46AM -0400, Martin Hicks wrote:
> >
> > Here's the promised sysctl to dump a node's pagecache. Please review!
> >
> > This patch depends on the zone reclaim atomic ops cleanup:
> > http://marc.theaimsgroup.com/?l=linux-mm&m=112307646306476&w=2
>
> Doesn't numactl --bind=node memhog nodesize-someslack do the same?
>
> It just might kick in the oom killer if someslack is too small
> or someone has unfreeable data there. But then there should be
> already an sysctl to turn that one off.
Doesn't the memhog hack also cause the machine to swap a lot? The
zone_reclaim() path doesn't let the memory reclaim code swap.
mh
--
Martin Hicks || Silicon Graphics Inc. || mort@sgi.com
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2005-08-03 14:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050801113913.GA7000@elte.hu>
[not found] ` <20050801102903.378da54f.akpm@osdl.org>
[not found] ` <20050801195426.GA17548@elte.hu>
[not found] ` <20050802171050.GG26803@localhost>
[not found] ` <20050802210746.GA26494@elte.hu>
2005-08-03 13:56 ` Martin Hicks
2005-08-03 14:15 ` Andi Kleen
2005-08-03 14:24 ` Martin Hicks [this message]
2005-08-03 14:38 ` Andi Kleen
2005-08-03 14:56 ` Martin Hicks
2005-08-03 19:59 ` Ray Bryant
2005-08-03 20:08 ` Andi Kleen
2005-08-05 17:45 ` Ray Bryant
2005-08-05 21:48 ` Andi Kleen
2005-08-15 16:05 ` 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=20050803142440.GQ26803@localhost \
--to=mort@sgi.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.org \
/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