mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Martin Hicks <mort@wildopensource.com>
Cc: pj@sgi.com, linux-kernel@vger.kernel.org, raybry@sgi.com
Subject: Re: [PATCH/RFC] A method for clearing out page cache
Date: Mon, 21 Feb 2005 13:42:20 -0800	[thread overview]
Message-ID: <20050221134220.2f5911c9.akpm@osdl.org> (raw)
In-Reply-To: <20050221192721.GB26705@localhost>

Martin Hicks <mort@wildopensource.com> wrote:
>
> This patch introduces a new sysctl for NUMA systems that tries to drop
>  as much of the page cache as possible from a set of nodes.  The
>  motivation for this patch is for setting up High Performance Computing
>  jobs, where initial memory placement is very important to overall
>  performance.

- Using a write to /proc for this seems a bit hacky.  Why not simply add
  a new system call for it?

- Starting a kernel thread for each node might be overkill.  Yes, it
  would take longer if one process was to do all the work, but does this
  operation need to be very fast?

  If it does, then userspace could arrange for that concurrency by
  starting a number of processes to perform the toss, each with a different
  nodemask.

- Dropping "as much pagecache as possible" might be a bit crude.  I
  wonder if we should pass in some additional parameter which specifies how
  much of the node's pagecache should be removed.

  Or, better, specify how much free memory we will actually require on
  this node.  The syscall terminates when it determines that enough
  pagecache has been removed.

- To make the syscall more general, we should be able to reclaim mapped
  pagecache and anonymous memory as well.


So what it comes down to is

sys_free_node_memory(long node_id, long pages_to_make_free, long what_to_free)

where `what_to_free' consists of a bunch of bitflags (unmapped pagecache,
mapped pagecache, anonymous memory, slab, ...).

  reply	other threads:[~2005-02-21 21:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14 15:44 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 [this message]
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
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=20050221134220.2f5911c9.akpm@osdl.org \
    --to=akpm@osdl.org \
    --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

all inboxes | Powered by JetHome®