[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f11576a0802090833h7a600ee8x87edb423cbbb5d79@mail.gmail.com>
Date: Sun, 10 Feb 2008 01:33:49 +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: [PATCH 0/8][for -mm] mem_notify v6
Hi
> Interesting patch series (I am being yuppie and reading this thread
> from my iPhone on a treadmill at the gym - so further comments later).
> I think that this is broadly along the lines that I was thinking, but
> this should be an RFC only patch series for now.
sorry, I fixed at next post.
> Some initial questions:
Thank you.
welcome to any discussion.
> Where is the netlink interface? Polling an FD is so last century :)
to be honest, I don't know anyone use netlink and why hope receive
low memory notify by netlink.
poll() is old way, but it works good enough.
and, netlink have a bit weak point.
end up, netlink philosophy is read/write model.
I afraid to many low-mem message queued in netlink buffer
at under heavy pressure.
it cause degrade memory pressure.
> Still, it is good to start with some code - eventually we might just
> have a full reservation API created. Rik and I and others have bounced
> ideas around for a while and I hope we can pitch in. I will play with
> these patches later.
Great.
Welcome to any idea and any discussion.
--
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