linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Minchan Kim <minchan.kim@gmail.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Minchan Kim <minchan.kim@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
	Matt Mackall <mpm@selenic.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] Kconfig: CONFIG_UNEVICTABLE_LRU move into EMBEDDED submenu
Date: Wed, 13 May 2009 19:12:21 +0900	[thread overview]
Message-ID: <20090513191221.674bc543.minchan.kim@barrios-desktop> (raw)
In-Reply-To: <20090513175539.723A.A69D9226@jp.fujitsu.com>

On Wed, 13 May 2009 17:59:34 +0900 (JST)
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:

> > Hi, Kosaki. 
> > 
> > On Wed, 13 May 2009 17:30:45 +0900 (JST)
> > KOSAKI Motohiro <kosaki.motohiro@jp.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.


Each people always have a different viewpoint. 
:) 

> 
> > > +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.

As I said previous(http://lkml.org/lkml/2009/3/16/209), Many embedded environment have a small ram. It doesn't have a big impact in such case. 

Let CCed embedded matainers. 
I won't have a objection if embedded maintainers ack this. 

Thanks for your effort for embdded. 

-- 
Kinds Regards
Minchan Kim

--
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:[~2009-05-13 10:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13  8:30 KOSAKI Motohiro
2009-05-13  8:51 ` Minchan Kim
2009-05-13  8:59   ` KOSAKI Motohiro
2009-05-13 10:12     ` Minchan Kim [this message]
2009-05-13 10:37       ` David Woodhouse
2009-05-13 11:13         ` Minchan Kim
2009-05-13 14:34         ` Matt Mackall
2009-05-13 14:45           ` David Woodhouse
2009-05-13 11:09 ` Andi Kleen
2009-05-13 11:18   ` KOSAKI Motohiro
2009-05-13 11:38     ` Andi Kleen
2009-05-13 11:41       ` Minchan Kim
2009-05-13 11:49         ` Andi Kleen
2009-05-13 11:58       ` KOSAKI Motohiro
2009-05-13 12:12         ` Minchan Kim
2009-05-13 14:13         ` Andi Kleen
2009-05-13 23:17           ` KOSAKI Motohiro
2009-05-13 11:24 ` Johannes Weiner

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=20090513191221.674bc543.minchan.kim@barrios-desktop \
    --to=minchan.kim@gmail.com \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=dwmw2@infradead.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mpm@selenic.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