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 for Android: free password hash cracker in your pocket

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

Message-ID: <20090513114907.GR19296@one.firstfloor.org>
Date:	Wed, 13 May 2009 13:49:07 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Minchan Kim <minchan.kim@...il.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	KOSAKI Motohiro <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>,
	Minchan@...stfloor.org
Subject: Re: [PATCH] Kconfig: CONFIG_UNEVICTABLE_LRU move into EMBEDDED submenu

On Wed, May 13, 2009 at 08:41:21PM +0900, Minchan Kim wrote:
> Hi, Andi.
> 
> On Wed, May 13, 2009 at 8:38 PM, Andi Kleen <andi@...stfloor.org> 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.
> 
> I thought this feature don't have a big impact on embedded.
> At First, 7K is not important but as time goes by, it could be huge

I don't follow. 7k is never huge, also not when time goes by.

In general saving text size is not very fruitful compared to the
savings you can get from optimizing dynamic memory allocation.
Most of the memory waste is in dynamic allocation. That's easy
to see because even on small systems there's much more (several
magnitudes) dynamic memory than kernel text.

-Andi
-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/