From: Andrew Morton <akpm@osdl.org>
To: Paul Jackson <pj@sgi.com>
Cc: mort@wildopensource.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 14:28:04 -0800 [thread overview]
Message-ID: <20050221142804.2b7de5ed.akpm@osdl.org> (raw)
In-Reply-To: <20050221141252.6b44f0ea.pj@sgi.com>
Paul Jackson <pj@sgi.com> wrote:
>
> Andrew wrote:
> > sys_free_node_memory(long node_id, long pages_to_make_free, long what_to_free)
> > ...
> > - To make the syscall more general, we should be able to reclaim mapped
> > pagecache and anonymous memory as well.
>
> sys_free_node_memory() - nice.
>
> Does it make sense to also have it be able to free up slab cache,
> calling shrink_slab()?
Yes, I suggested that slab be one of the `what_to_free' flags. (Some of
this may be tricky to implement. But a good interface with an
initially-crappy implementation is OK ;)
> Did you mean to pass a nodemask, or a single node id? Passing a single
> node id is easier - we've shown that it is difficult to pass bitmaps
> across the user/kernel boundary without confusions. But if only a
> single node id is passed, then you get the thread per node that you just
> argued was sometimes overkill.
I meant a single node ID. With a bitmap, the kernel needs to futz around
scanning the bitmap, launching kernel threads, etc.
I'm proposing that there be no kernel threads at all. If you have four nodes:
for i in 0 1 2 3
do
call-sys_free_node_memory $i -1 -1 &
done
> I'd prefer the single node id, because it's easier to get right.
yup.
next prev parent reply other threads:[~2005-02-21 22:28 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
2005-02-21 22:12 ` Paul Jackson
2005-02-21 22:28 ` Andrew Morton [this message]
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=20050221142804.2b7de5ed.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
Powered by JetHome