From: Daniel J Blueman <daniel@numascale-asia.com>
To: Borislav Petkov <bp@amd64.org>
Cc: Steffen Persvold <sp@numascale.com>, X86-ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <borislav.petkov@amd.com>
Subject: Re: [PATCH] x86, AMD, NB: Cleanup and improve NB descriptors handling
Date: Tue, 16 Oct 2012 22:12:55 +0800 [thread overview]
Message-ID: <507D6B67.2010009@numascale-asia.com> (raw)
In-Reply-To: <1350396375-26896-1-git-send-email-bp@amd64.org>
On 16/10/2012 22:06, Borislav Petkov wrote:
> From: Borislav Petkov <borislav.petkov@amd.com>
>
> First of all, the double loop of first counting the northbridges on
> the system, then allocating them and then going over them again was
> bugging me for a long time now. Fix it by moving the allocation of the
> descriptors in the initial iteration path.
>
> Then, modify the enclosing _info structure to contain two NB descriptor
> structures: and array of 8 NB descs which contains the first 8 possible
> NB descriptors for all single-board AMD systems out there. This is no
> different from the current state of affairs and is done this way so that
> lookup of those descriptors remains fast.
>
> Then, there's a linked list of further NB descs which are for large,
> confederated systems like NumaScale where more than 8 nodes are present
> in the fabric and are visible to the single system Linux image. We keep
> those unique by introducing the PCI domain ID into the node ID used for
> descriptor lookup.
>
> Rest of the code is cleanup and readability improvements.
[...]
Looks good.
I recall there were some other areas that needed fixing, so I'll rebase
on top of this tomorrow and present my change so far.
Thanks,
Daniel
--
Daniel J Blueman
Principal Software Engineer, Numascale Asia
prev parent reply other threads:[~2012-10-16 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 14:06 [PATCH] x86, AMD, NB: Cleanup and improve NB descriptors handling Borislav Petkov
2012-10-16 14:12 ` Daniel J Blueman [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=507D6B67.2010009@numascale-asia.com \
--to=daniel@numascale-asia.com \
--cc=borislav.petkov@amd.com \
--cc=bp@amd64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sp@numascale.com \
--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