linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: Add /proc/sys/vm/drop_node_caches
Date: Thu, 25 May 2006 17:31:39 -0700	[thread overview]
Message-ID: <20060525173139.036356bf.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0605251706350.27460@schroedinger.engr.sgi.com>

Christoph Lameter <clameter@sgi.com> wrote:
>
> On Thu, 25 May 2006, Andrew Morton wrote:
> 
> > If we're talking about some formal, supported access to the kernel's NUMA
> > facilities then poking away at /proc doesn't seem a particularly good way
> > of doing it.  The application _should_ be able to set its memory policy to
> > point at that node and get all the old caches evicted automatically.  If
> > that doesn't work, what's wrong?
> 
> zone_reclaim does exactly that for an application. So that case is 
> covered.
> 
> However, there are situations in which someone wants to insure that there 
> is no pagecache on some nodes (testing and some special apps).

What situations?  Why doesn't zone_reclaim suit in those cases?

We'd need considerably more detail to be able to justify a hacky thing like
this please.  Bear in mind that if we do this and people start using it then

a) that'll cause us to avoid doing it properly (however that is)

b) if people are using this /proc hack to work around inadequacies in
   the NUMA support then it'll decrease the pressure on us to fix up that
   numa support.

c) it's something we'll need to support for ever and ever.

--
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>

  reply	other threads:[~2006-05-26  0:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-25 23:56 Christoph Lameter
     [not found] ` <20060525170509.331aaf2d.akpm@osdl.org>
2006-05-26  0:10   ` Christoph Lameter
2006-05-26  0:31     ` Andrew Morton [this message]
2006-05-26  1:23       ` Christoph Lameter

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=20060525173139.036356bf.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=linux-mm@kvack.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