From: "Måns Rullgård" <mans@mansr.com>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, "Måns Rullgård" <mans@mansr.com>,
linux-kernel@vger.kernel.org
Subject: Re: [discuss] Dropping CONFIG_REORDER on x86-64 for 2.6.22
Date: Fri, 20 Apr 2007 18:24:42 +0100 [thread overview]
Message-ID: <yw1xr6qf7ycl.fsf@thrashbarg.mansr.com> (raw)
In-Reply-To: <200704201137.45799.ak@suse.de> (Andi Kleen's message of "Fri, 20 Apr 2007 11:37:45 +0200")
Andi Kleen <ak@suse.de> writes:
> On Friday 20 April 2007 10:35:10 Måns Rullgård wrote:
>> Arjan van de Ven <arjan@linux.intel.com> writes:
>>
>> > Andi Kleen wrote:
>> >> Rationale:
>> >> - It cannot be enabled in normal builds because all current lds
>> >> become very slow when they have to handle thousands of sections.
>> >>
>> >
>> > afaik this is only ever reported on SuSE; I've not heard it on any
>> > other distro...
>>
>> Even with that option set, the full kernel build with my configuration
>> finishes in one minute flat on my Gentoo box. Could it be that the
>> linker uses enormous amounts of memory? I have 4GB so I wouldn't
>> immediately notice.
>
> What binutils version do you use? Maybe that particular problem is
> finally fixed. Of course would still leave the other issues I
> listed.
I'm using the Gentoo default, which is 2.16.1 plus some patches. A
quick scan of the patches suggests that perhaps this one has something
to do with it:
http://sources.redhat.com/ml/binutils/2005-03/msg00847.html
--
Måns Rullgård
mans@mansr.com
next prev parent reply other threads:[~2007-04-20 17:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 11:54 Andi Kleen
2007-04-19 14:27 ` Arjan van de Ven
2007-04-19 16:59 ` Chuck Ebbert
2007-04-20 8:35 ` Måns Rullgård
2007-04-20 9:37 ` [discuss] " Andi Kleen
2007-04-20 17:24 ` Måns Rullgård [this message]
2007-04-19 17:06 ` Adrian Bunk
2007-04-19 20:10 ` David Miller
2007-04-20 1:21 ` Herbert Xu
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=yw1xr6qf7ycl.fsf@thrashbarg.mansr.com \
--to=mans@mansr.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.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®