netdev - Re: igb bandwidth allocation configuration

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: <4AB0F1BD.4020206@voltaire.com>
Date:	Wed, 16 Sep 2009 17:10:05 +0300
From:	Or Gerlitz <ogerlitz@...taire.com>
To:	Alexander Duyck <alexander.h.duyck@...el.com>
CC:	Simon Horman <horms@...ge.net.au>,
	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Alexander Duyck <alexander.duyck@...il.com>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
Subject: Re: igb bandwidth allocation configuration

Alexander Duyck wrote:
> The interface for all of this would make sense as part of a virtual 
> ethernet switch control which is the way I am currently leaning on all 
> this.
Yes, you can say that out of the per VF <mac, vlan-id, priority, rate> 
tuple I mentioned, except for the mac, the other parameters actually 
belong to the egress flow of the virtual switch port this VF is 
connected to. So the vswitch actually signs the packet with vlan+pbits 
and enforces the rate. Now vswitch can be software based, or hardware 
NIC based.

Now, I assume there may be NICs which will let you configure the 
<vlan-id, priority, rate> as part of the their virtual switch config, 
but others, e.g
the 82576 as an example, and following our discussion, will let you do 
that for the VF, in the VF driver which as you said may run the guest OS 
where we can't control it...

Or.


--
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