From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: [PATCH] topology for ia64
Date: Tue, 22 Oct 2002 00:07:30 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805203@msgid-missing> (raw)
>>>>> On Sat, 5 Oct 2002 19:04:22 +0200, Erich Focht <efocht@ess.nec.de> said:
Erich> Hi David, please find attached a first attempt to implement
Erich> the topology.h macros/routines for IA64. We need this for the
Erich> NUMA scheduler setup.
Why does the cpu_to_node_map[] exist for non-NUMA configurations? It
seems to me that it would be better to make cpu_to_node_map a macro
that uses an array-check for NUMA configurations and a simple test
against phys_cpu_present_map() for non-NUMA.
--david
next reply other threads:[~2002-10-22 0:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 0:07 David Mosberger [this message]
2002-10-22 9:23 ` [Linux-ia64] Re: [PATCH] topology for ia64 Erich Focht
2002-10-29 22:19 ` Matthew Dobson
2002-10-29 22:35 ` Michael Hohnbaum
2002-10-29 23:43 ` Erich Focht
2002-10-29 23:55 ` Matthew Dobson
2002-10-30 0:01 ` Matthew Dobson
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=marc-linux-ia64-105590709805203@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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