From: Andi Kleen <ak@suse.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: larger per cpu data
Date: Fri, 20 Apr 2007 22:11:58 +0200 [thread overview]
Message-ID: <200704202211.58419.ak@suse.de> (raw)
In-Reply-To: <617E1C2C70743745A92448908E030B2A015F22CB@scsmsx411.amr.corp.intel.com>
On Friday 20 April 2007 20:23:13 Luck, Tony wrote:
> > I heard there were some problems with ia64 have those been fixed too?
>
> IA64 has a 64KB page allocated for each cpu for the percpu data. Right
> now we are using 28K-32K for the arch/ia64/configs/* variations.
Could that be enlarged without too much trouble?
> > Anybody would have a problem with increasing per CPU data in a
> > standard kernel by a few KB?
>
> How many is "a few" ... and much more importantly is your few KB
> a fixed amount, or does it scale up with the number of network cards
> (or anything else that there might be a lot of on a large system)?
> A fixed extra 8-10K should be fine. #NIC * 1K would cause problems.
There are scalable parts, but those would likely stay allocated.
==
-Andi
next prev parent reply other threads:[~2007-04-20 20:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 10:46 larger per cpu data Andi Kleen
2007-04-20 18:23 ` Luck, Tony
2007-04-20 20:11 ` Andi Kleen [this message]
2007-04-20 20:23 ` Luck, Tony
2007-04-24 17:14 ` Jes Sorensen
2007-04-24 17:58 ` Luck, Tony
2007-04-24 18:03 ` Jes Sorensen
2007-04-21 20:23 ` Eric W. Biederman
2007-04-21 20:46 ` Andi Kleen
2007-04-21 20:53 ` Eric W. Biederman
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=200704202211.58419.ak@suse.de \
--to=ak@suse.de \
--cc=linux-arch@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).