netdev - Re: [PATCH] NET: Multiqueue network device support.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070612.150450.17595071.davem@davemloft.net>
Date:	Tue, 12 Jun 2007 15:04:50 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jeff@...zik.org
Cc:	rdreier@...co.com, greearb@...delatech.com, netdev@...r.kernel.org,
	kaber@...sh.net, hadi@...erus.ca, peter.p.waskiewicz.jr@...el.com,
	auke-jan.h.kok@...el.com
Subject: Re: [PATCH] NET: Multiqueue network device support.

From: Jeff Garzik <jeff@...zik.org>
Date: Tue, 12 Jun 2007 17:59:43 -0400

> And where shall we put the configuration machinery, to support sub-queues?
> Shall we duplicate the existing configuration code for sub-queues?
> What will ifconfig/ip usage look like?
> How will it differ from configurating full net_devices, if you are 
> assigning the same types of parameters?

If you're asking about the virtualization scenerio, the
control node (dom0 or whatever) is the only entity which
can get at programming the filters and will set it up
properly based upon which parts of the physical device
are being exported to which guest nodes.

For the non-virtualized case, it's a good question.

But really the current hardware is just about simple queue steering,
and simple static DRR/WRED fairness algorithms applied to the queues
in hardware.

We don't need to add support for configuring anything fancy from the
start just to get something working.  Especially the important bits
such as the virtualization case and the interrupt and queue
distribution case on SMP.  The latter can even be configured
automatically by the driver, and that's in fact what I expect
drivers to do initially.

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html