From: David Miller <davem@davemloft.net>
To: therbert@google.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] net: Changes in queue allocation and freeing
Date: Mon, 15 Nov 2010 10:58:22 -0800 (PST) [thread overview]
Message-ID: <20101115.105822.233710935.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.1.00.1011091240470.18565@pokey.mtv.corp.google.com>
From: Tom Herbert <therbert@google.com>
Date: Tue, 9 Nov 2010 12:47:26 -0800 (PST)
> Changes to both RX and TX queue allocation. In both cases allocate
> in alloc_netdev_mq and free in free_netdev. For RX the reference
> couting also changed, the device reference count can now be used.
Both applied, with the comment removal added as promised.
I assume you'll spin a new version of the XPS patches
against this?
Thanks!
next prev parent reply other threads:[~2010-11-15 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 20:47 [PATCH 0/2] net: Changes in queue allocation and freeing Tom Herbert
2010-11-10 10:41 ` Eric Dumazet
2010-11-10 16:27 ` Tom Herbert
2010-11-10 21:00 ` David Miller
2010-11-15 18:58 ` David Miller [this message]
2010-11-15 21:04 ` Tom Herbert
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=20101115.105822.233710935.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.com \
/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).