mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Joe Perches <joe@perches.com>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Greg Kroah-Hartman <gregkh@suse.de>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 03/07] kernel.h string cleanup
Date: Fri, 26 Feb 2010 09:27:24 -0500	[thread overview]
Message-ID: <1267194445.6328.111.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <a8e1da1002260155l5e75a473oca5649ab33cce124@mail.gmail.com>

On Fri, 2010-02-26 at 17:55 +0800, Dave Young wrote:

> Spliting is necessary from my point of view.

> 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
> 
> vmlinux .text size: 003bfcea

Why the change in text size? If moving stuff around in headers affects
the final result, I'm thinking that you did something wrong.

The merge for x86 did a lot of file manipulation, but Thomas and Ingo
would always test that the binary result was the same. If the binary
result is different, then something went wrong with the file
manipulations.

-- Steve




  parent reply	other threads:[~2010-02-26 14:27 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
2010-02-26 10:51               ` Dave Young
2010-02-26 14:27             ` Steven Rostedt [this message]
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=1267194445.6328.111.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=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 \
    /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®