[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090513175539.723A.A69D9226@jp.fujitsu.com>
Date: Wed, 13 May 2009 17:59:34 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: Minchan Kim <minchan.kim@...il.com>
Cc: kosaki.motohiro@...fujitsu.com,
LKML <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Lee Schermerhorn <Lee.Schermerhorn@...com>
Subject: Re: [PATCH] Kconfig: CONFIG_UNEVICTABLE_LRU move into EMBEDDED submenu
> Hi, Kosaki.
>
> On Wed, 13 May 2009 17:30:45 +0900 (JST)
> KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> wrote:
>
> > Subject: [PATCH] Kconfig: CONFIG_UNEVICTABLE_LRU move into EMBEDDED submenu
> >
> > Almost people always turn on CONFIG_UNEVICTABLE_LRU. this configuration is
> > used only embedded people.
>
> I think at least embedded guys don't need it.
> But I am not sure other guys.
perhaps, I and you live in another embedded world.
> > +config UNEVICTABLE_LRU
> > + bool "Add LRU list to track non-evictable pages" if EMBEDDED
> > + default y
>
> If you want to move, it would be better as following.
>
> config UNEVICTABLE_LRU
> bool "Add LRU list to track non-evictable pages" if EMBEDDED
> default !EMBEDDED
No.
As far as I know, many embedded guys use this configuration.
they hate unexpected latency by reclaim. !UNEVICTABLE_LRU increase
unexpectability largely.
--
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