From: Alexey Dobriyan <adobriyan@gmail.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Joe Perches <joe@perches.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Greg Kroah-Hartman <gregkh@suse.de>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 03/07] kernel.h string cleanup
Date: Fri, 26 Feb 2010 11:58:40 +0200 [thread overview]
Message-ID: <b6fcc0a1002260158k59117d7cib3ed7fc72afff86d@mail.gmail.com> (raw)
In-Reply-To: <a8e1da1002260155l5e75a473oca5649ab33cce124@mail.gmail.com>
On Fri, Feb 26, 2010 at 11:55 AM, Dave Young <hidave.darkstar@gmail.com> wrote:
> It will be more clean to put externs/declarations to their own header files.
> At the same time compiling time benifits as well.
>
> printk/panic/string/trace header are splited then included by kernel.h so
> just hexdump/int_sqrt are actually seperated.
>
> fresh boot
You mean cold-cache compile so results are basically random?
> and same .config, make without -j, test result as following:
>
> with the patches applied:
>
> time:
> real 15m16.504s
> user 12m51.866s
> sys 1m39.700s
>
> vmlinux .text size: 003bfcd2
>
> without the patches applied*
> time:
> real 15m20.518s
> user 12m54.120s
> sys 1m40.190s
Not scientific at all.
next prev parent reply other threads:[~2010-02-26 9:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 15:53 Dave Young
2010-02-25 18:55 ` Alexey Dobriyan
2010-02-26 1:14 ` Dave Young
2010-02-26 7:15 ` Alexey Dobriyan
2010-02-26 7:33 ` Dave Young
2010-02-26 7:42 ` Joe Perches
2010-02-26 9:55 ` Dave Young
2010-02-26 9:58 ` Alexey Dobriyan [this message]
2010-02-26 10:51 ` Dave Young
2010-02-26 14:27 ` Steven Rostedt
2010-02-27 9:55 ` Dave Young
2010-02-27 10:20 ` Frederic Weisbecker
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=b6fcc0a1002260158k59117d7cib3ed7fc72afff86d@mail.gmail.com \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=gregkh@suse.de \
--cc=hidave.darkstar@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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
Powered by JetHome