linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH 1/1] network memory allocator.
Date: Tue, 15 Aug 2006 22:21:22 +0200	[thread overview]
Message-ID: <200608152221.22883.arnd@arndb.de> (raw)
In-Reply-To: <20060814110359.GA27704@2ka.mipt.ru>

Am Monday 14 August 2006 13:04 schrieb Evgeniy Polyakov:
> ?* full per CPU allocation and freeing (objects are never freed on
> ????????different CPU)

Many of your data structures are per cpu, but your underlying allocations
are all using regular kzalloc/__get_free_page/__get_free_pages functions.
Shouldn't these be converted to calls to kmalloc_node and alloc_pages_node
in order to get better locality on NUMA systems?

OTOH, we have recently experimented with doing the dev_alloc_skb calls
with affinity to the NUMA node that holds the actual network adapter, and
got significant improvements on the Cell blade server. That of course
may be a conflicting goal since it would mean having per-cpu per-node
page pools if any CPU is supposed to be able to allocate pages for use
as DMA buffers on any node.

	Arnd <><

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2006-08-15 20:21 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 11:04 Evgeniy Polyakov
2006-08-14 11:22 ` David Miller, Evgeniy Polyakov
2006-08-14 11:32   ` Evgeniy Polyakov
2006-08-14 11:40 ` Andi Kleen
2006-08-14 11:46   ` Evgeniy Polyakov
2006-08-14 12:07 ` Keith Owens
2006-08-14 12:20   ` Evgeniy Polyakov
2006-08-14 17:42     ` Rick Jones
2006-08-14 20:15       ` David Miller, Rick Jones
2006-08-14 12:25 ` Peter Zijlstra
2006-08-14 12:35   ` Evgeniy Polyakov
2006-08-14 12:38     ` Evgeniy Polyakov
2006-08-15 10:55     ` Peter Zijlstra
2006-08-15 11:26       ` Evgeniy Polyakov
2006-08-15 12:03         ` Peter Zijlstra
2006-08-15 12:34           ` Evgeniy Polyakov
2006-08-15 13:49             ` Peter Zijlstra
2006-08-15 14:15               ` Evgeniy Polyakov
2006-08-15 14:48                 ` Peter Zijlstra
2006-08-15 15:05                   ` Evgeniy Polyakov
2006-08-15 15:07                     ` Evgeniy Polyakov
2006-08-15 17:42                     ` Peter Zijlstra
2006-08-15 17:49                       ` Evgeniy Polyakov
2006-08-16  2:52                 ` Bill Fink
2006-08-16  5:38                   ` Evgeniy Polyakov
2006-08-14 17:46 ` Rick Jones
2006-08-14 19:42   ` Evgeniy Polyakov
2006-08-15  7:27 ` Andrew Morton
2006-08-15  8:08   ` Andi Kleen
2006-08-15 10:02     ` Evgeniy Polyakov
2006-08-15 10:27       ` David Miller, Evgeniy Polyakov
2006-08-15  9:20   ` Evgeniy Polyakov
2006-08-15 20:21 ` Arnd Bergmann [this message]
2006-08-16  5:35   ` Evgeniy Polyakov
2006-08-16  8:48     ` Christoph Hellwig
2006-08-16  9:00       ` Evgeniy Polyakov
2006-08-16  9:05         ` David Miller, Evgeniy Polyakov
2006-08-16  9:10           ` Christoph Hellwig
2006-08-16  9:32             ` Evgeniy Polyakov
2006-08-16  9:38               ` Christoph Hellwig
2006-08-16  9:40                 ` David Miller, Christoph Hellwig
2006-08-16  9:44                   ` Christoph Hellwig
2006-08-16  9:42         ` Christoph Hellwig
2006-08-16 11:27         ` Arnd Bergmann
2006-08-16 12:00           ` Evgeniy Polyakov
2006-08-16 12:25       ` Andi Kleen
2006-08-18  2:25         ` Christoph Lameter
2006-08-18  9:29           ` Andi Kleen
2006-08-18  8:51             ` David Miller, Andi Kleen
2006-08-18 17:04             ` Christoph Lameter
2006-08-16  7:51 ` [PATCH2 " Evgeniy Polyakov
2006-08-16 16:57   ` Stephen Hemminger
2006-08-16 19:27     ` Evgeniy Polyakov

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=200608152221.22883.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=johnpol@2ka.mipt.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=netdev@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