public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: raybry@sgi.com, mort@wildopensource.com, pj@sgi.com,
	linux-kernel@vger.kernel.org, hilgeman@sgi.com,
	Andi Kleen <ak@suse.de>
Subject: Re: [PATCH/RFC] A method for clearing out page cache
Date: Tue, 22 Feb 2005 09:24:54 +0100	[thread overview]
Message-ID: <20050222082454.GA2401@elte.hu> (raw)
In-Reply-To: <20050222000710.5ad0d8c1.akpm@osdl.org>


* Andrew Morton <akpm@osdl.org> wrote:

> >  . enable users to
> >  specify an 'allocation priority' of some sort, which kicks out the
> >  pagecache on the local node - or something like that.
> 
> Yes, that would be preferable - I don't know what the difficulty is
> with that.  sys_set_mempolicy() should provide a sufficiently good
> hint.

yes. I'm not against some flushing mechanism for debugging or test
purposes (it can be useful to start from a new, clean state - and as
such the sysctl for root only and depending on KERNEL_DEBUG is probably
better than an explicit syscall), but the idea to give a flushing API to
applications is bad i believe.

It is the 'easy and incorrect path' to a number of NUMA (and non-NUMA)
VM problems and i fear that it will destroy the evolution of VM
priority/placement/affinity APIs (NUMAlib, etc.).

At least making it sufficiently painful to use (via the originally
proposed root-only sysctl) could still preserve some of the incentive to
provide a clean solution for applications. 'Time to market' constraints
should not be considered when adding core mechanisms.

	Ingo

  reply	other threads:[~2005-02-22  8:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14 15:44 [PATCH/RFC] A method for clearing out page cache Martin Hicks
2005-02-15  3:37 ` Paul Jackson
2005-02-16 19:56   ` Martin Hicks
2005-02-21 19:27   ` Martin Hicks
2005-02-21 21:42     ` Andrew Morton
2005-02-21 22:12       ` Paul Jackson
2005-02-21 22:28         ` Andrew Morton
2005-02-21 23:52           ` Paul Jackson
2005-02-21 22:28       ` Ray Bryant
2005-02-21 22:41         ` Andrew Morton
2005-02-21 23:01           ` Ray Bryant
2005-02-22  7:53           ` Ingo Molnar
2005-02-22  8:07             ` Andrew Morton
2005-02-22  8:24               ` Ingo Molnar [this message]
2005-02-22 17:29                 ` Ray Bryant
2005-02-22 11:26             ` Paul Jackson
2005-02-22 18:45               ` Andrew Morton
2005-02-22 18:59                 ` Martin Hicks
2005-02-22 19:03                 ` Ray Bryant
2005-02-23  0:14                 ` Paul Jackson
2005-03-01 21:54       ` Pavel Machek
2005-02-21 21:52     ` Nish Aravamudan

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=20050222082454.GA2401@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=hilgeman@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mort@wildopensource.com \
    --cc=pj@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