From: Stephen Hemminger <shemminger@linux-foundation.org>
To: "Sreenivasa Honnur" <Sreenivasa.Honnur@neterion.com>
Cc: "Kok, Auke" <auke-jan.h.kok@intel.com>,
"David Miller" <davem@davemloft.net>,
"Garzik, Jeff" <jgarzik@pobox.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
"Peter Waskiewicz Jr" <peter.p.waskiewicz.jr@intel.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"Kok, Auke" <auke@foo-projects.org>,
"Ronciak, John" <john.ronciak@intel.com>
Subject: Re: [PATCH 1/2] NET: Multiple queue network device support
Date: Fri, 23 Feb 2007 11:19:11 -0800 [thread overview]
Message-ID: <20070223111911.75602c0f@freekitty> (raw)
In-Reply-To: <78C9135A3D2ECE4B8162EBDCE82CAD77013F383F@nekter>
On Fri, 23 Feb 2007 04:00:55 -0500
"Sreenivasa Honnur" <Sreenivasa.Honnur@neterion.com> wrote:
> Fucntion "map_queue" returns queue index as '0'. There is no support to
> return different queue indexes.
>
> -----Original Message-----
> From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.org]
> On Behalf Of Kok, Auke
> Sent: Friday, February 09, 2007 5:40 AM
> To: David Miller; Garzik, Jeff; netdev@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Cc: Kok, Auke; Peter Waskiewicz Jr; Brandeburg, Jesse; Kok, Auke;
> Ronciak, John
> Subject: [PATCH 1/2] NET: Multiple queue network device support
>
>
> From: Peter Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
>
> Added an API and associated supporting routines for multiqueue network
> devices. This allows network devices supporting multiple TX queues to
> configure each queue within the netdevice and manage each queue
> independantly. Changes to the PRIO Qdisc also allow a user to map
> multiple flows to individual TX queues, taking advantage of each queue
> on the device.
>
> Signed-off-by: Peter Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
> Signed-off-by: Auke Kok <auke-jan.h.kok@intel.com>
> ---
>
> +config NET_MULTI_QUEUE_DEVICE
> + bool "Multiple queue network device support (EXPERIMENTAL)"
> + depends on NET_SCHED && EXPERIMENTAL
> + help
> + Saying Y here will add support for network devices that have
> more than
> + one physical TX queue and/or RX queue.
> +
> + Multiple queue devices will require qdiscs that understand how
> to
> + queue to multiple targets. The default packet scheduler will
> default
> + to the first queue in a device. In other words, if you need
> the
> + ability to spread traffic across queues, your queueing
> discipline
> + needs to know how to do that.
> +
> + Note that saying Y here will give preferential treatment to
> multiple
> + queue devices in the network stack. A slight drop in
> single-queue
> + device performance may be seen.
> +
> + Say N here unless you know your network device supports
> multiple
> + TX and/or RX queues.
> +
This should not be a user visible configuration option.
It should either: always be part of the kernel API
or be selected by drivers that need/want it.
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-02-23 19:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 9:00 [PATCH 1/2] NET: Multiple queue network device support Sreenivasa Honnur
2007-02-23 19:05 ` Waskiewicz Jr, Peter P
2007-02-23 19:19 ` Stephen Hemminger [this message]
2007-02-23 19:23 ` Kok, Auke
-- strict thread matches above, loose matches on Subject: below --
2007-02-23 9:02 Sreenivasa Honnur
2007-02-09 0:09 [PATCH 0/2 REVIEW] Multiple transmit/receive queue kernel Kok, Auke
2007-02-09 0:09 ` [PATCH 1/2] NET: Multiple queue network device support Kok, Auke
2007-02-27 1:03 ` David Miller
2007-02-27 19:38 ` Waskiewicz Jr, Peter P
2007-03-07 22:18 ` Waskiewicz Jr, Peter P
2007-03-07 22:42 ` David Miller
2007-03-09 7:26 ` Jarek Poplawski
2007-03-09 13:40 ` Thomas Graf
2007-03-09 19:25 ` Waskiewicz Jr, Peter P
2007-03-09 23:01 ` Thomas Graf
2007-03-09 23:27 ` Waskiewicz Jr, Peter P
2007-03-10 2:34 ` Thomas Graf
2007-03-10 20:37 ` Waskiewicz Jr, Peter P
2007-03-12 8:58 ` Jarek Poplawski
2007-03-12 20:21 ` Waskiewicz Jr, Peter P
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=20070223111911.75602c0f@freekitty \
--to=shemminger@linux-foundation.org \
--cc=Sreenivasa.Honnur@neterion.com \
--cc=auke-jan.h.kok@intel.com \
--cc=auke@foo-projects.org \
--cc=davem@davemloft.net \
--cc=jesse.brandeburg@intel.com \
--cc=jgarzik@pobox.com \
--cc=john.ronciak@intel.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;
as well as URLs for NNTP newsgroup(s).