public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Maksym Planeta <mcsim.planeta@gmail.com>,
	mingo@redhat.com, kernel-janitors@vger.kernel.org,
	namhyung@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86: page: get_order() optimization
Date: Sun, 27 Mar 2011 18:22:22 +0200	[thread overview]
Message-ID: <201103271822.22851.PeterHuewe@gmx.de> (raw)
In-Reply-To: <20110327113323.GA27825@elte.hu>

Am Sonntag 27 März 2011, 13:33:23 schrieb Ingo Molnar:
> 
> Just wondering, what's the before/after 'size vmlinux' effect on a 'make
> defconfig' x86 kernel? Does the optimization make the kernel smaller as
> well, besides making it faster?
> 
> Thanks,
> 
> 	Ingo
Hi,

I compiled Linus' Tree (40471856) on my x86_64 machine, once without the patch 
and once with the patch.


size vmlinux-with*
   text    data     bss     dec     hex filename
7996901 1236036 1118208 10351145         9df229 vmlinux-withoutpatch
7996554 1235988 1118208 10350750         9df09e vmlinux-withpatch

ls -la vmlinux-with*
-rwxr-xr-x 1 peter users 18921237 27. Mär 17:40 vmlinux-withoutpatch
-rwxr-xr-x 1 peter users 18921333 27. Mär 17:58 vmlinux-withpatch



Peter 


  reply	other threads:[~2011-03-27 16:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-27  8:45 [PATCH v2] x86: page: get_order() optimization Maksym Planeta
2011-03-27 11:33 ` Ingo Molnar
2011-03-27 16:22   ` Peter Hüwe [this message]
2011-03-27 17:15   ` Maksym Planeta
2011-03-28  5:08     ` Ingo Molnar
2011-03-28 19:33       ` Maksym Planeta
2011-03-28 19:44         ` H. Peter Anvin
2011-04-01 14:08           ` Maksym Planeta
2011-03-28 19:47 ` H. Peter Anvin
2011-03-29  7:27   ` Ingo Molnar

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=201103271822.22851.PeterHuewe@gmx.de \
    --to=peterhuewe@gmx.de \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcsim.planeta@gmail.com \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=namhyung@gmail.com \
    /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