From: David Miller <davem@davemloft.net>
To: peter.p.waskiewicz.jr@intel.com
Cc: jeb.j.cramer@intel.com, christopher.leech@intel.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
jgarzik@pobox.com, auke-jan.h.kok@intel.com
Subject: Re: [PATCH] NET: Multiqueue network device support, replayed.
Date: Thu, 05 Apr 2007 14:35:27 -0700 (PDT) [thread overview]
Message-ID: <20070405.143527.63129672.davem@davemloft.net> (raw)
In-Reply-To: <D5C1322C3E673F459512FB59E0DDC329029ADBC2@orsmsx414.amr.corp.intel.com>
From: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
Date: Thu, 5 Apr 2007 14:33:19 -0700
> David,
> Please consider pulling from my git tree:
>
> git-pull git://lost.foo-projects.org/~ppwaskie/git/net-2.6.22
> multiqueue
>
> This is a branch named 'multiqueue' of a recent pull from your tree with
> an updated implementation of the multiqueue implementation we've been
> working on. Included in this is:
>
> 1) A simplified API where all drivers will allocate a queue struct for
> each queue on the NIC.
> 2) A transparent stack change for both non-mq and mq devices to use the
> same codepath.
> 3) Remove the per-queue locking model, and just use the per-queue
> netif_{start|stop|wake}_subqueue() functions for multiqueue management.
> 4) Updated multiqueue documentation in Documentation/networking
> describing the implementation and base driver requirements to implement
> multiqueue support.
Thanks for following up on this work, but it really needs to be
reviewed here on netdev, I really can't just pull this into my
tree until it is reviewed properly here.
So, please post the new feature as a set of patches.
Thanks a lot.
prev parent reply other threads:[~2007-04-05 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 21:33 Waskiewicz Jr, Peter P
2007-04-05 21:35 ` David Miller [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=20070405.143527.63129672.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=auke-jan.h.kok@intel.com \
--cc=christopher.leech@intel.com \
--cc=jeb.j.cramer@intel.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.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
all inboxes | Powered by JetHome®