From: Christoph Lameter <clameter@sgi.com>
To: Mike Travis <travis@sgi.com>
Cc: arges@linux.vnet.ibm.com, phil.el@wanadoo.fr, mpjohn@us.ibm.com,
Jack Steiner <steiner@sgi.com>, Paul Jackson <pj@sgi.com>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Hotplug CPU support for Oprofile
Date: Mon, 5 May 2008 12:12:56 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0805051211110.11469@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <481F5965.6070305@sgi.com>
The allocpercpu approach creates a pointer array and results in objects
distributed over all of memory. A cpu alloc approach would place
dynamically allocated per cpu objects together which is better for memory
consumption (no need to align) and performance (same TLB entry, neigboring
memory cells, possible shared cachelines).
prev parent reply other threads:[~2008-05-05 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1210012443.6374.23.camel@snuffleupagus>
2008-05-05 19:00 ` Mike Travis
2008-05-05 19:12 ` Christoph Lameter [this message]
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=Pine.LNX.4.64.0805051211110.11469@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=arges@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mpjohn@us.ibm.com \
--cc=phil.el@wanadoo.fr \
--cc=pj@sgi.com \
--cc=steiner@sgi.com \
--cc=travis@sgi.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
all inboxes | Powered by JetHome®