All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: davidm@hpl.hp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] per-cpu change
Date: Fri, 2 May 2003 21:53:22 -0700	[thread overview]
Message-ID: <20030503045322.GI8978@holomorphy.com> (raw)
In-Reply-To: <20030503044617.DE0642C003@lists.samba.org>

In message <16050.41490.798865.517036@napali.hpl.hp.com> you write:
>>  - On NUMA, you want to allocate the per-CPU areas in node-local memory.

On Sat, May 03, 2003 at 02:40:57PM +1000, Rusty Russell wrote:
> Thanks: I'd forgotten about this.  Even "big smp" machines often have
> different memory latencies.

I have already a patch to do this for ia32 NUMA systems (which present
issues not present on sane architectures).

I also didn't notice the lack of an override; #undef'ing the macro
__GENERIC_PER_CPU appeared to suffice for me.


-- wli

      reply	other threads:[~2003-05-03  4:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02  8:28 [PATCH] per-cpu change Rusty Russell
2003-05-02 16:51 ` David Mosberger
2003-05-03  4:40   ` Rusty Russell
2003-05-03  4:53     ` William Lee Irwin III [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=20030503045322.GI8978@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=davidm@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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.