From: Robin Holt <holt@sgi.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: ia64 allmodconfig on current mainline
Date: Fri, 15 Aug 2008 07:01:13 -0500 [thread overview]
Message-ID: <20080815120113.GN6824@sgi.com> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA30844B247@orsmsx505.amr.corp.intel.com>
On Tue, Aug 12, 2008 at 05:21:09PM -0700, Luck, Tony wrote:
> > /opt/crosstool/gcc-3.4.5-glibc-2.3.6/ia64-unknown-linux-gnu/bin/ia64-unknown-linux-gnu-ld: section .data [0000000004ea0000 -> 0000000004f656e7] overlaps section .data.percpu [0000000004e90000 -> 0000000004ea0d17]
>
> This means there is too much DEFINE_PER_CPU() going on. Current
> ia64 limit for the sum of all per cpu objects is 64K. For a
> build using defconfig we seem to be close (56K/64K ... look for
> the address of __per_cpu_end and see how close it is to the top
> of the address space: 0xffffffffffffffff).
Not sure if anybody is looking into this. Just tried a compile of generic
and allmod. The differences are not that significant with the exception
of per_cpu__kmem_cache_cpu at 0x28a0. A couple other low-hanging fruit
here are per_cpu__shadow_flush_counts and per_cpu__mmu_gathers each of
which takes approx 16k.
Thanks,
Robin
next prev parent reply other threads:[~2008-08-15 12:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080812150608.231a948a.akpm@linux-foundation.org>
2008-08-12 22:22 ` ia64 allmodconfig on current mainline Rafael J. Wysocki
2008-08-12 22:58 ` Andrew Morton
2008-08-13 0:21 ` Luck, Tony
2008-08-15 12:01 ` Robin Holt [this message]
2008-08-15 16:11 ` Luck, Tony
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=20080815120113.GN6824@sgi.com \
--to=holt@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tony.luck@intel.com \
/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