[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080115110918.118B.KOSAKI.MOTOHIRO@jp.fujitsu.com>
Date: Tue, 15 Jan 2008 11:20:56 +0900
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc: kosaki.motohiro@...fujitsu.com, linux-mm@...ck.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>
Subject: Re: [RFC][PATCH 3/5] add /dev/mem_notify device
Hi Kame
> > + if (pressure) {
> > + nr_wakeup = max_t(int, atomic_read(&nr_watcher_task)>>4, 100);
> > + atomic_long_set(&last_mem_notify, jiffies);
> > + wake_up_locked_nr(&mem_wait, nr_wakeup);
> > + }
> What is this for ? and Why ?
> Are there too many waiters ?
my intent is for avoid thundering herd.
100 is heuristic value.
and too many wakeup cause too much memory freed.
I don't want it.
of course, if any problem happened, I will change.
Do you dislike it?
--
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