[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <28c262360903160555u402b4c34nf273951a207826a2@mail.gmail.com>
Date: Mon, 16 Mar 2009 21:55:03 +0900
From: Minchan Kim <minchan.kim@...il.com>
To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc: Christoph Hellwig <hch@...radead.org>,
David Howells <dhowells@...hat.com>, lee.schermerhorn@...com,
akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH] Point the UNEVICTABLE_LRU config option at the
documentation
size vmlinux
text data bss dec hex filename
6232681 747665 708608 7688954 7552fa vmlinux
size vmlinux.unevictable
text data bss dec hex filename
6239404 747985 708608 7695997 756e7d vmlinux.unevictable
It almost increases about 7K.
Many embedded guys always have a concern about size although it is very small.
It's important about embedded but may not be about server.
In addition, CONFIG_UNEVICTABLE_LRU feature don't have a big impact in
embedded machines which have a very small ram.
I guess many embedded guys will not use this feature.
So, I don't want to remove this configurable option.
Lets not add useless size bloat in embedded system.
On Mon, Mar 16, 2009 at 9:22 PM, KOSAKI Motohiro
<kosaki.motohiro@...fujitsu.com> wrote:
>> On Mon, Mar 16, 2009 at 10:59:45AM +0000, David Howells wrote:
>> > Point the UNEVICTABLE_LRU config option at the documentation describing the
>> > option.
>>
>> Didn't we decide a while ago that the option is pointless and the code
>> should always be enabled?
>
> Yeah.
> CONFIG_UNEVICTABLE_LRU lost existing reason by David's good patch recently.
>
> if nobody of nommu user post bug report in .30 age, I plan to remove
> this config option at .31 age.
>
> his patch is really really good job.
>
>
>
>
--
Kinds regards,
Minchan Kim
--
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