linux-kernel - Re: [PATCH] Kconfig: CONFIG_UNEVICTABLE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 May 2009 21:12:06 +0900
From:	Minchan Kim <minchan.kim@...il.com>
To:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-mm <linux-mm@...ck.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Lee Schermerhorn <Lee.Schermerhorn@...com>,
	Minchan@...stfloor.org
Subject: Re: [PATCH] Kconfig: CONFIG_UNEVICTABLE_LRU move into EMBEDDED 
	submenu

On Wed, May 13, 2009 at 8:58 PM, KOSAKI Motohiro
<kosaki.motohiro@...fujitsu.com> wrote:
>>> In past days, I proposed this. but Minchan found this config bloat kernel 7kb
>>> and he claim embedded guys should have selectable chance. I agreed it.
>>
>> Well there's lots of code in the kernel and 7k doesn't seem worth bothering.
>> If you just save two pages of memory somewhere you can save more.
>>
>>> Is this enough explanation?
>>
>> It's not a very good one.
>>
>> I would propose to just remove it or at least hide it completely
>> and only make it dependent on CONFIG_MMU inside Kconfig.
>
> hm, if minchan ack this, I can remove this option completely.

In fact, I expected this feature has to be disable with default.
But, David and Hannes already acked with enable with default.

It means they don't have a size concern, too.
Hmm. If I don't misunderstood their thought, I agree Andi's suggestion.

Thanks for good discussion. Andi!

-- 
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/