From: "H. Peter Anvin" <hpa@zytor.com>
To: Daniel Blueman <daniel@numascale-asia.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Steffen Persvold <sp@numascale.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Borislav Petkov <bp@amd64.org>,
x86@kernel.org
Subject: Re: [PATCH] RFC: Fix AMD Northbridge-ID contiguity assumptions
Date: Wed, 03 Oct 2012 08:50:51 -0700 [thread overview]
Message-ID: <506C5EDB.9000107@zytor.com> (raw)
In-Reply-To: <CAP-4_fVhkjb=0YdYz37PEg3Or-hbRO8F40tHqEsRCC-pYY_HOg@mail.gmail.com>
On 10/03/2012 08:30 AM, Daniel Blueman wrote:
> >
> > Is that "on NumaScale systems"? If so, please say so rather than trying
> > to make it sound generic; if it is not, can you give some other examples?
>
> It is for Numascale (NumaChip) systems for our purposes.
>
> Any other systems which interconnect Opterons via address space routing
> (needed for >8 HT nodes) will get this benefit. I can't put my hand to
> exactly what is out there, but can find out.
>
The reason I'm asking is because it is an important bit of the record of
the code to know if this is a specific need or a general need. This may
be obvious now, but 5-10 years from now someone will need to know why or
what.
The two paragraphs above is exactly what is needed, i.e. "NumaChip or
any other design which shares these specific design features: ..."
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-10-03 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 9:20 [PATCH] RFC: Fix AMD Northbridge-ID contiguity assumptions Daniel J Blueman
2012-10-03 15:16 ` H. Peter Anvin
[not found] ` <CAP-4_fVhkjb=0YdYz37PEg3Or-hbRO8F40tHqEsRCC-pYY_HOg@mail.gmail.com>
2012-10-03 15:50 ` H. Peter Anvin [this message]
2012-10-03 18:08 ` Borislav Petkov
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=506C5EDB.9000107@zytor.com \
--to=hpa@zytor.com \
--cc=bp@amd64.org \
--cc=daniel@numascale-asia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sp@numascale.com \
--cc=tglx@linutronix.de \
--cc=x86@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