linux-kernel - Re: [PATCH] Point the UNEVICTABLE_LRU config option at the documentation

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] [day] [month] [year] [list]

Date:	Mon, 16 Mar 2009 22:14:11 +0900
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	Minchan Kim <minchan.kim@...il.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

2009/3/16 Minchan Kim <minchan.kim@...il.com>:
> 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.

Thanks good report.
this is unintetional size to me. I'll digg it later.

Thanks!


-- kosaki


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