From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Minchan Kim <minchan.kim@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
David Howells <dhowells@redhat.com>,
lee.schermerhorn@hp.com, akpm@linux-foundation.org,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] Point the UNEVICTABLE_LRU config option at the documentation
Date: Mon, 16 Mar 2009 22:14:11 +0900 [thread overview]
Message-ID: <2f11576a0903160614n4908d0fdo25df387dd724ac19@mail.gmail.com> (raw)
In-Reply-To: <28c262360903160555u402b4c34nf273951a207826a2@mail.gmail.com>
2009/3/16 Minchan Kim <minchan.kim@gmail.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, 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>
prev parent reply other threads:[~2009-03-16 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 10:59 David Howells
2009-03-16 12:02 ` Christoph Hellwig
2009-03-16 12:22 ` KOSAKI Motohiro
2009-03-16 12:55 ` Minchan Kim
2009-03-16 13:14 ` KOSAKI Motohiro [this message]
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=2f11576a0903160614n4908d0fdo25df387dd724ac19@mail.gmail.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=lee.schermerhorn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=torvalds@linux-foundation.org \
/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