From: Jes Sorensen <jes@sgi.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Andi Kleen <ak@suse.de>, linux-arch@vger.kernel.org
Subject: Re: larger per cpu data
Date: 24 Apr 2007 13:14:49 -0400 [thread overview]
Message-ID: <yq0odldpud2.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <617E1C2C70743745A92448908E030B2A015F2383@scsmsx411.amr.corp.intel.com>
>>>>> "Tony" == Luck, Tony <tony.luck@intel.com> writes:
>> > 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?
Tony> If we stick to mapping it with a single TLB entry, then the next
Tony> size up is 256K ... which is a pretty big jump. But the code
Tony> that does the mapping is just about to be changed from a single
Tony> locked TLB entry to a map-on-tlb-miss version (thanks to Ken
Tony> Chen). Some small-ish additions to that code would allow an
Tony> expansion to 128K by mapping each half with a 64K TLB entry on
Tony> demand.
256KB * 1024 CPUs (or more) == verymightyhuge ..... I certainly
wouldn't like to see this.
Cheers,
Jes
next prev parent reply other threads:[~2007-04-24 17:37 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
2007-04-20 20:23 ` Luck, Tony
2007-04-24 17:14 ` Jes Sorensen [this message]
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=yq0odldpud2.fsf@jaguar.mkp.net \
--to=jes@sgi.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.