From: Christoph Hellwig <hch@lst.de>
To: akpm@osdl.org, davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH 0/3] node-aware skb allocations
Date: Wed, 15 Nov 2006 18:36:43 +0100 [thread overview]
Message-ID: <20061115173643.GA17695@lst.de> (raw)
This is the final version of the node-aware skb allocations,
implementing davem's suggestion of storing the numa node in
struct device. I'd love to get this into 2.6.20 now that I
don't hear negative comments about it anymre, but I wonder
how. The first patch toches mm/slab.c, the second struct device
and assorted files and only the last one is actually in the networking
code. Should Dave push all this through net-2.6.20 or should we
get it in purely through -mm?
--
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>
next reply other threads:[~2006-11-15 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 17:36 Christoph Hellwig [this message]
2006-11-15 23:16 ` Andrew Morton
2006-11-16 10:53 ` David Miller, Andrew Morton
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=20061115173643.GA17695@lst.de \
--to=hch@lst.de \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--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