From: Chuck Ebbert <cebbert@redhat.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Andi Kleen <ak@suse.de>,
discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: Dropping CONFIG_REORDER on x86-64 for 2.6.22
Date: Thu, 19 Apr 2007 12:59:44 -0400 [thread overview]
Message-ID: <4627A000.1030509@redhat.com> (raw)
In-Reply-To: <46277C36.6030301@linux.intel.com>
Arjan van de Ven wrote:
> 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...
It's horribly slow on Fedora.
next prev parent reply other threads:[~2007-04-19 16:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 11:54 Dropping CONFIG_REORDER on x86-64 for 2.6.22 Andi Kleen
2007-04-19 14:27 ` Arjan van de Ven
2007-04-19 16:59 ` Chuck Ebbert [this message]
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
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=4627A000.1030509@redhat.com \
--to=cebbert@redhat.com \
--cc=ak@suse.de \
--cc=arjan@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).