public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org,
	torvalds@osdl.org, akpm@osdl.org
Subject: Re: [Patch 2/4] Basic reorder infrastructure - makes linking very slow
Date: Fri, 10 Mar 2006 10:45:57 +0100	[thread overview]
Message-ID: <200603101045.58667.ak@suse.de> (raw)
In-Reply-To: <1141060775.2992.149.camel@laptopd505.fenrus.org>

On Monday 27 February 2006 18:19, Arjan van de Ven wrote:
> On Mon, 2006-02-27 at 17:31 +0100, sam@ravnborg.org wrote:
> > > This patch puts the infrastructure in place to allow for a reordering of
> > > functions based inside the vmlinux.
> > 
> > Can we make this general instead of x86_64 only?
> > Then we can use Kconfig to enable it for the architectures where we want it.
> 
> Actually Linus had pretty good arguments to make this per-architecture:
> the list will be different on each architecture.
> 
> (eg my first patch had it more generic; but Linus asked it to be per
> arch, and I agree with the reasons he gave)
> 
> Also I doubt it can be enabled "blindly" for all architectures; I expect
> more to need hacks similar to the x86_64 entry.S fix before it can
> work...

Hi,

I just discovered that this patch is the reason why my compiles slowed
down so dramatically (thanks to Michael M. for the hint) 
The SUSE 10.0 ld goes from running in seconds to more than a minute.

I think I will drop this patch for now because I doubt the
runtime improvement is worth the compile slowdown.

If there is some binutils  release that handles this without dramatic
slowdown we can test for it in the Makefile, but i don't want it 
to be enabled by default.

-Andi


  parent reply	other threads:[~2006-03-10 17:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 15:23 [Patch 0/4] Reordering of functions, try 2 Arjan van de Ven
2006-02-27 15:27 ` [Patch 2/4] Basic reorder infrastructure Arjan van de Ven
2006-02-27 15:41   ` Andi Kleen
2006-02-27 16:31   ` sam
2006-02-27 17:19     ` Arjan van de Ven
2006-02-28 19:08       ` Sam Ravnborg
2006-03-10  9:45       ` Andi Kleen [this message]
2006-02-27 15:31 ` [Patch 4/4] Tell GCC 4.1 to move unlikely() code to a separate section Arjan van de Ven
2006-02-27 15:39   ` Andi Kleen
2006-02-27 23:33     ` Bill Davidsen
2006-02-27 15:31 ` [Patch 3/4] Move the base kernel to 2Mb to align with TLB boundaries Arjan van de Ven
2006-02-27 15:36   ` Andi Kleen
2006-02-27 15:52     ` Arjan van de Ven
2006-02-27 15:31 ` [Patch 1/4] avoid entry.S functions from reordering Arjan van de Ven
2006-02-27 15:36 ` [Patch 0/4] Reordering of functions, try 2 Andi Kleen
2006-02-27 15:43   ` Arjan van de Ven

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=200603101045.58667.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@osdl.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