From: Andi Kleen <ak@suse.de>
To: tony.luck@intel.com
Cc: linux-arch@vger.kernel.org
Subject: larger per cpu data
Date: Fri, 20 Apr 2007 12:46:17 +0200 [thread overview]
Message-ID: <200704201246.17531.ak@suse.de> (raw)
Hi,
I've been looking at optimizing the network per CPU statistics and the best way to
do that would be to move them back to direct per CPU data. Currently they are
allocated separately because there used to be some trouble on x86 (and ia64?)
with limited per CPU areas. At least the x86 side has been fixed now. I heard
there were some problems with ia64 have those been fixed too?
Anybody would have a problem with increasing per CPU data in a standard kernel
by a few KB?
-Andi
next reply other threads:[~2007-04-20 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 10:46 Andi Kleen [this message]
2007-04-20 18:23 ` larger per cpu data Luck, Tony
2007-04-20 20:11 ` Andi Kleen
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=200704201246.17531.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).