From: Ingo Molnar <mingo@elte.hu>
To: Andreas Herrmann <andreas.herrmann3@amd.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
jbarnes@virtuousgeek.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: fixup numa_node information for AMD CPU northbridge functions
Date: Fri, 17 Apr 2009 18:14:45 +0200 [thread overview]
Message-ID: <20090417161445.GE8253@elte.hu> (raw)
In-Reply-To: <20090417100746.GG16198@alberich.amd.com>
* Andreas Herrmann <andreas.herrmann3@amd.com> wrote:
> Currently the numa_node attribute for these PCI devices is 0 (it
> corresponds to the numa_node for PCI bus 0). This is not a big issue
> but incorrect.
>
> This inconsistency can be fixed by reading the node number from CPU
> NB function 0.
>
> Signed-off-by: Andreas Herrmann <andreas.herrmann3@amd.com>
> ---
> arch/x86/kernel/quirks.c | 35 +++++++++++++++++++++++++++++++++++
> 1 files changed, 35 insertions(+), 0 deletions(-)
applied, thanks. Note, i added this impact line to the commit:
[ Impact: fill in dev->numa_node information, to optimize DMA allocations ]
as numa_node does matter to certain DMA allocations such as
dma_generic_alloc_coherent() - we (try to) allocate node-local
memory in that case.
pci_dev::numa_node might be used for more such optimizations in the
future - so it's generally good to have this filled in correctly.
So it's more than just a fix for an inconsistency.
Ingo
next prev parent reply other threads:[~2009-04-17 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 10:07 [PATCH] x86: fixup numa_node information for AMD CPU northbridge functions Andreas Herrmann
2009-04-17 16:14 ` Ingo Molnar [this message]
2009-04-17 16:27 ` [tip:x86/cpu] " tip-bot for Andreas Herrmann
2009-04-17 19:22 ` Yinghai Lu
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=20090417161445.GE8253@elte.hu \
--to=mingo@elte.hu \
--cc=andreas.herrmann3@amd.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@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