linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Marcelo Tosatti <marcelo@kvack.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Daniel Spang <daniel.spang@gmail.com>,
	Rik van Riel <riel@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH 3/5] add /dev/mem_notify device
Date: Wed, 16 Jan 2008 12:42:34 +0100	[thread overview]
Message-ID: <20080116114234.GA22460@elf.ucw.cz> (raw)
In-Reply-To: <20080116041332.GA30877@dmt>

On Wed 2008-01-16 02:13:32, Marcelo Tosatti wrote:
> On Wed, Jan 16, 2008 at 10:57:16AM +0900, KOSAKI Motohiro wrote:
> > Hi Pavel
> > 
> > > > 	err = poll(&pollfds, 1, -1); // wake up at low memory
> > > > 
> > > >         ...
> > > > </usage example>
> > > 
> > > Nice, this is really needed for openmoko, zaurus, etc....
> > > 
> > > But this changelog needs to go into Documentation/...
> > > 
> > > ...and /dev/mem_notify is really a bad name. /dev/memory_low?
> > > /dev/oom?
> > 
> > thank you for your kindful advise.
> > 
> > but..
> > 
> > to be honest, my english is very limited.
> > I can't make judgments name is good or not.
> > 
> > Marcelo, What do you think his idea?
> 
> "mem_notify" sounds alright, but I don't really care.
> 
> Notify:
> 
> To give notice to; inform: notified the citizens of the curfew by
> posting signs.

I'd read mem_notify as "tell me when new memory is unplugged" or
something. /dev/oom_notify? Plus, /dev/ names usually do not have "_"
in them.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-01-16 11:42 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15  0:52 [RFC][PATCH 0/5] mem notifications v4 KOSAKI Motohiro
2008-01-15  0:59 ` [RFC][PATCH 1/5] introduce poll_wait_exclusive() new API KOSAKI Motohiro
2008-01-15  1:00 ` [RFC][PATCH 2/5] introduce wake_up_locked_nr() " KOSAKI Motohiro
2008-01-15  1:01 ` [RFC][PATCH 3/5] add /dev/mem_notify device KOSAKI Motohiro
2008-01-15  1:08   ` Randy Dunlap
2008-01-15  1:20     ` KOSAKI Motohiro
2008-01-15  1:24       ` KOSAKI Motohiro
2008-01-15  2:10   ` KAMEZAWA Hiroyuki
2008-01-15  2:20     ` KOSAKI Motohiro
2008-01-15  2:56       ` Rik van Riel
2008-01-15 10:46   ` Alan Cox
2008-01-15 10:59     ` KOSAKI Motohiro
2008-01-15 11:20       ` Alan Cox
2008-01-15 11:48         ` KOSAKI Motohiro
2008-01-15 13:42           ` Alan Cox
2008-01-16  2:43             ` KOSAKI Motohiro
2008-01-15 12:05         ` Marcelo Tosatti
2008-01-15 13:42           ` Alan Cox
2008-01-15 22:16   ` Pavel Machek
2008-01-16  1:57     ` KOSAKI Motohiro
2008-01-16  4:13       ` Marcelo Tosatti
2008-01-16 11:42         ` Pavel Machek [this message]
2008-01-16 11:51           ` Daniel Spång
2008-01-17  3:04             ` KOSAKI Motohiro
2008-01-15  1:02 ` [RFC][PATCH 4/5] memory_pressure_notify() caller KOSAKI Motohiro
2008-01-15  2:06   ` KAMEZAWA Hiroyuki
2008-01-15  2:37     ` KOSAKI Motohiro
2008-01-15  3:00       ` KAMEZAWA Hiroyuki
2008-01-15  3:08         ` KOSAKI Motohiro
2008-01-15 22:55   ` Daniel Spång
2008-01-15 22:59     ` Rik van Riel
2008-01-15 23:39       ` Daniel Spång
2008-01-16  1:48         ` KOSAKI Motohiro
2008-01-16 11:03           ` Daniel Spång
2008-01-17  3:26             ` KOSAKI Motohiro
2008-01-18 10:24               ` Daniel Spång
2008-01-18 10:30                 ` KOSAKI Motohiro
2008-01-15  1:03 ` [RFC][PATCH 5/5] /proc/zoneinfo enhancement KOSAKI Motohiro
2008-01-15 10:44   ` Alan Cox
2008-01-15 10:49     ` KOSAKI Motohiro

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=20080116114234.GA22460@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@linux-foundation.org \
    --cc=daniel.spang@gmail.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@kvack.org \
    --cc=riel@redhat.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