This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: [PATCH] xen network backend driver

On Wed, 2011-01-19 at 21:58 +0200, Pasi Kärkkäinen wrote:
> On Wed, Jan 19, 2011 at 07:48:19PM +0000, Ben Hutchings wrote:
> > It was possible to use multiple receive queues per device long before
> > this since the networking core is not involved in locking them.  (Though
> > it did require some hacks to create multiple NAPI contexts, before
> > 2.6.24.)  This is mostly useful useful in conjunction with separate IRQs
> > per RX queue, spread across multiple CPUs (sometimes referred to as
> > Receive Side Scaling or RSS).
> > 
> Ok. I should read changelogs more closely.. I thought both the 
> receive/transmit 
> multiqueue features appeared 'recently', but it seems I was wrong.

There was a relatively recent change that allows drivers to record which
receive queue each packet came in on.  This is used by RPS/RFS, and for
transmit queue selection when bridging/forwarding.  But multiple receive
queues were still usable before that.

> I think Linux 2.6.32 added multiqueue VLAN support..

VLAN devices and several other types of software device don't have
queues of their own, but they can now use all transmit queues of the
underlying device rather than just one.


Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

Xen-devel mailing list