All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Christoph Lameter <christoph@lameter.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
	shai@scalex86.org
Subject: Re: [PATCH] NUMA aware allocation of transmit and receive buffers for e1000
Date: Wed, 18 May 2005 15:19:34 +0200	[thread overview]
Message-ID: <m1oeb86595.fsf@muc.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0505172125210.22920@graphe.net> (Christoph Lameter's message of "Tue, 17 May 2005 21:27:48 -0700 (PDT)")

Christoph Lameter <christoph@lameter.com> writes:

> On Tue, 17 May 2005, David S. Miller wrote:
>
>> > Because physically contiguous memory is usually better than virtually 
>> > contiguous memory? Any reason that physically contiguous memory will 
>> > break the driver?
>> 
>> The issue is whether size can end up being too large for
>> kmalloc() to satisfy, whereas vmalloc() would be able to
>> handle it.
>
> Oww.. We need a NUMA aware vmalloc for this?  

You can do that already by just changing process NUMA policy temporarily
while calling vmalloc.

-Andi

  parent reply	other threads:[~2005-05-18 13:19 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         ` Andi Kleen [this message]
2005-05-18  2:05 ` [PATCH] NUMA aware allocation of transmit and receive buffers for e1000 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

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=m1oeb86595.fsf@muc.de \
    --to=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=christoph@lameter.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.