[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f11576a0802090846t7655e988pb1b712696cad1098@mail.gmail.com>
Date: Sun, 10 Feb 2008 01:46:06 +0900
From: "KOSAKI Motohiro" <kosaki.motohiro@...fujitsu.com>
To: "Jon Masters" <jonathan@...masters.org>
Cc: "linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Marcelo Tosatti" <marcelo@...ck.org>,
"Daniel Spang" <daniel.spang@...il.com>,
"Rik van Riel" <riel@...hat.com>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Alan Cox" <alan@...rguk.ukuu.org.uk>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"Pavel Machek" <pavel@....cz>, "Al Boldi" <a1426z@...ab.com>,
"Zan Lynx" <zlynx@....org>
Subject: Re: [sample] mem_notify v6: usage example
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!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists