From: Andi Kleen <ak@muc.de>
To: Christoph Lameter <christoph@lameter.com>
Cc: Eric Dumazet <dada1@cosmosbay.com>,
netdev@oss.sgi.com, akpm@osdl.org, shai@scalex86.org
Subject: Re: [PATCH] NUMA aware allocation of transmit and receive buffers for e1000
Date: 30 May 2005 11:41:07 +0200
Date: Mon, 30 May 2005 11:41:07 +0200 [thread overview]
Message-ID: <20050530094107.GJ86087@muc.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0505271413560.25484@graphe.net>
On Fri, May 27, 2005 at 02:15:55PM -0700, Christoph Lameter wrote:
> On Wed, 18 May 2005, Eric Dumazet wrote:
>
> > Related question, is pci_alloc_consistent() already NUMA aware ?
>
> Nope. It also ultimately acquires memory via vmalloc.
x86-64 vmalloc has been NUMA aware forever.
I believe the HP BigTux patchkit for IA64 added it there too, although
it might not have hit mainline.
>
> pci_alloc_consistent will also need some rework to allocate memory
> consistent (well the name is coherent right?) with the node that the
> device is on. Second case of a need for a node aware vmalloc?
You can already have it today by temporarily changing the process
mempolicy. However for pci_alloc_consistent just using alloc_pages_node
directly seems to work fine.
-Andi
prev parent reply other threads:[~2005-05-30 9:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 1:56 [PATCH] NUMA aware allocation of transmit and receive buffers for e1000 Christoph Lameter
2005-05-18 2:03 ` Andrew Morton
2005-05-18 2:52 ` Christoph Lameter
2005-05-18 2:57 ` David S. Miller
2005-05-18 4:27 ` Christoph Lameter
2005-05-18 4:58 ` Andrew Morton
2005-05-18 15:55 ` Ganesh Venkatesan
2005-05-18 20:42 ` Andrew Morton
2005-05-27 21:52 ` [PATCH] e1000: NUMA aware allocation of descriptors V2 Christoph Lameter
2005-05-27 23:25 ` Andrew Morton
2005-05-18 13:19 ` [PATCH] NUMA aware allocation of transmit and receive buffers for e1000 Andi Kleen
2005-05-18 2:05 ` Andi Kleen
2005-05-18 7:49 ` Eric Dumazet
2005-05-18 13:28 ` Andi Kleen
2005-05-27 21:15 ` Christoph Lameter
2005-05-30 9:41 ` Andi Kleen [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=20050530094107.GJ86087@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=christoph@lameter.com \
--cc=dada1@cosmosbay.com \
--cc=netdev@oss.sgi.com \
--cc=shai@scalex86.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;
as well as URLs for NNTP newsgroup(s).