From: "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>
To: "Jon Masters" <jonathan@jonmasters.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Marcelo Tosatti" <marcelo@kvack.org>,
"Daniel Spang" <daniel.spang@gmail.com>,
"Rik van Riel" <riel@redhat.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"Pavel Machek" <pavel@ucw.cz>, "Al Boldi" <a1426z@gawab.com>,
"Zan Lynx" <zlynx@acm.org>
Subject: Re: [sample] mem_notify v6: usage example
Date: Sun, 10 Feb 2008 01:46:06 +0900 [thread overview]
Message-ID: <2f11576a0802090846t7655e988pb1b712696cad1098@mail.gmail.com> (raw)
In-Reply-To: <CE520A17-98F2-4A08-82AB-C3D5061616A1@jonmasters.org>
Hi Jon
> This really needs to be triggered via a generic kernel event in the
> final version - I picture glibc having a reservation API and having
> generic support for freeing such reservations.
to be honest, I doubt idea of generic reservation framework.
end up, we hope drop the application cache, not also dataless memory.
but, automatically drop mechanism only able to drop dataless memory.
and, many application have own memory management subsystem.
I afraid to nobody use too complex framework.
What do you think it?
I hope see your API. please post it.
Thanks!
next prev parent reply other threads:[~2008-02-09 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 15:55 [sample] mem_notify v6: usage example KOSAKI Motohiro
2008-02-09 16:07 ` Jon Masters
2008-02-09 16:46 ` KOSAKI Motohiro [this message]
2008-02-11 18:15 ` Andreas Dilger
2008-02-11 18:37 ` KOSAKI Motohiro
2008-02-10 1:30 ` Pavel Machek
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=2f11576a0802090846t7655e988pb1b712696cad1098@mail.gmail.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=a1426z@gawab.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=daniel.spang@gmail.com \
--cc=jonathan@jonmasters.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo@kvack.org \
--cc=pavel@ucw.cz \
--cc=riel@redhat.com \
--cc=zlynx@acm.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;
as well as URLs for NNTP newsgroup(s).