mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: akpm@linux-foundation.org
Cc: paulmck@linux.vnet.ibm.com, fweisbec@gmail.com,
	josh@joshtriplett.org, eparis@redhat.com,
	paul.gortmaker@windriver.com, vapier@gentoo.org,
	kyungsik.lee@lge.com, jslaby@suse.cz, dwight.engen@oracle.com,
	pefoley2@pefoley.com, linux-kernel@vger.kernel.org,
	Michael Opdenacker <michael.opdenacker@free-electrons.com>
Subject: [PATCH 0/1] init/Kconfig: improve CC_OPTIMIZE_FOR_SIZE documentation
Date: Thu, 24 Apr 2014 14:07:33 +0200	[thread overview]
Message-ID: <1398341254-4626-1-git-send-email-michael.opdenacker@free-electrons.com> (raw)

This patch proposes to warn users about the negative performance
impact of CC_OPTIMIZE_FOR_SIZE (compiling with -Os instead of -O2).
For the moment, we are just advising users not to select this option,
but extra details would be useful.

I made some experiments with this option. All of them yielded
degraded overall boot time. The kernel is smaller and hence is copied
and started earlier, but the benefits are quickly offset by the
slower kernel code. Even the total boot time is usually worse
than with a regular kernel.

Here are my latest results, on Atmel SAMA5D3 Xplained (ARM),
Linux 3.10, gzip compressed kernel:

Timestamp		O2		Os		Diff
Starting kernel 	4.307 s 	5.593 s 	-94 ms
Starting init		4.213 s 	5.549 s 	-44 ms
Login prompt		21.085 s	22.900 s 	+1.815 s 

Michael Opdenacker (1):
  init/Kconfig: improve CC_OPTIMIZE_FOR_SIZE documentation

 init/Kconfig | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

-- 
1.8.3.2


             reply	other threads:[~2014-04-24 12:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 12:07 Michael Opdenacker [this message]
2014-04-24 12:07 ` [PATCH 1/1] " Michael Opdenacker
2014-04-24 15:06   ` Josh Triplett
2014-04-24 14:55 ` [PATCH 0/1] " Josh Triplett
2014-04-24 19:34   ` Michael Opdenacker

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=1398341254-4626-1-git-send-email-michael.opdenacker@free-electrons.com \
    --to=michael.opdenacker@free-electrons.com \
    --cc=akpm@linux-foundation.org \
    --cc=dwight.engen@oracle.com \
    --cc=eparis@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=jslaby@suse.cz \
    --cc=kyungsik.lee@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=pefoley2@pefoley.com \
    --cc=vapier@gentoo.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

all inboxes | Powered by JetHome®