linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: [PATCH 0/8][for -mm] mem_notify v6
Date: Sun, 10 Feb 2008 01:33:49 +0900	[thread overview]
Message-ID: <2f11576a0802090833h7a600ee8x87edb423cbbb5d79@mail.gmail.com> (raw)
In-Reply-To: <B846E82A-D513-40CD-A19C-B60653569269@jonmasters.org>

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.

  reply	other threads:[~2008-02-09 16:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09 15:19 [PATCH 0/8][for -mm] mem_notify v6 KOSAKI Motohiro
2008-02-09 16:02 ` Jon Masters
2008-02-09 16:33   ` KOSAKI Motohiro [this message]
2008-02-09 16:43     ` Rik van Riel
2008-02-09 16:49       ` KOSAKI Motohiro
2008-02-11 15:36 ` [PATCH 0/8][for -mm] mem_notify v6, " Jonathan Corbet
2008-02-11 15:46   ` KOSAKI Motohiro
2008-02-17 14:49 ` Paul Jackson
2008-02-19  7:36   ` KOSAKI Motohiro
2008-02-19 15:00     ` Paul Jackson
2008-02-19 19:02       ` Rik van Riel
2008-02-19 20:18         ` Paul Jackson
2008-02-19 20:43           ` Paul Jackson
2008-02-19 22:28       ` Pavel Machek
2008-02-20  1:54         ` Paul Jackson
2008-02-20  2:07         ` Rik van Riel
2008-02-20  2:48           ` KOSAKI Motohiro
2008-02-20  4:57             ` Paul Jackson
2008-02-20  5:21               ` KOSAKI Motohiro
2008-02-20  4:36           ` Paul Jackson
2008-04-01 23:35 ` Tom May

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=2f11576a0802090833h7a600ee8x87edb423cbbb5d79@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).