From: "Kok, Auke" <auke-jan.h.kok@intel•com>
To: David Miller <davem@davemloft•net>
Cc: auke-jan.h.kok@intel•com, shemminger@linux-foundation•org,
netdev@vger•kernel.org
Subject: Re: [RFC] restore netdev_priv optimization (planb)
Date: Fri, 17 Aug 2007 18:48:06 -0700 [thread overview]
Message-ID: <46C64FD6.6030902@intel.com> (raw)
In-Reply-To: <20070817.183008.38712695.davem@davemloft.net>
David Miller wrote:
> From: "Kok, Auke" <auke-jan.h.kok@intel•com>
> Date: Fri, 17 Aug 2007 18:21:25 -0700
>
>> this sounds highly optimistic ("64 queues is enough for everyone"?)
>> and probably will be quickly outdated by both hardware and demand...
>
> As such drivers appear in the tree we can adjust the value.
>
> Even the most aggressively multi-queued virtualization and 10GB
> ethernet chips I am aware of, both in production and in development,
> do not exceed this limit.
>
> Since you think this is worth complaining about, you must know of some
> exceptions? :-)
I actually don't, but I assume that demand for queues will quickly increase once
the feature becomes available. e.g. in e1000 hardware (pci-e) we support 2, and
this is really old hardware already (laugh), 82575 has 4.
the ixgbe driver me and Ayyappan posted already supports 64 rx queues and 32 tx...
I can only expect the next generation to take a bigger jump and implement at
least 128 queues... :)
Auke
next prev parent reply other threads:[~2007-08-18 1:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 22:40 [RFC] restore netdev_priv optimization Stephen Hemminger
2007-08-17 23:04 ` David Miller
2007-08-17 23:19 ` Stephen Hemminger
2007-08-17 23:56 ` David Miller
2007-08-18 0:49 ` [RFC] restore netdev_priv optimization (planb) Stephen Hemminger
2007-08-18 1:00 ` David Miller
2007-08-18 1:21 ` Kok, Auke
2007-08-18 1:28 ` Stephen Hemminger
2007-08-18 1:31 ` David Miller
2007-08-18 1:30 ` David Miller
2007-08-18 1:48 ` Kok, Auke [this message]
2007-08-20 11:51 ` [RFC] restore netdev_priv optimization Benjamin Thery
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=46C64FD6.6030902@intel.com \
--to=auke-jan.h.kok@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shemminger@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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