netdev - [net-next-2.6 PATCH v2 0/4] dcbnl: Extending dcbnl to support non-host DCBX

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-next>] [day] [month] [year] [list]

Date:	Thu, 30 Dec 2010 18:26:42 +0200
From:	"Shmulik Ravid" <shmulikr@...adcom.com>
To:	davem@...emloft.net
cc:	"Eilon Greenstein" <eilong@...adcom.com>,
	"John Fastabend" <john.r.fastabend@...el.com>, lucy.liu@...el.com,
	netdev@...r.kernel.org
Subject: [net-next-2.6 PATCH v2 0/4] dcbnl: Extending dcbnl to support
 non-host DCBX

DCBX is the exchange protocol for negotiating DCB parameters between a
host and a switch. In some circumstances the DCBX negotiator can not
reside in the host directly on top of the networking interface. For
instance many converged network adapters support an embedded DCBX engine
that performs the negotiation and configures the device with the
negotiated parameters. Another example is virtual hosts and SRIOV
virtual functions.

The following patches extend the dcbnl netlink interface so in addition
to its current semantics it offers a standard mechanism for managing
such non-host DCBX engines. In this new mode 'set' operations are used
to set the initial negotiation configuration and the 'get' operation are
used to retrieve the negotiated results. 

The current definition of dcbnl assumes a host based stack is performing
the negotiation. As DCBX is encapsulated by LLDP there can be only one
DCBX negotiator per physical link. Thus the current scheme does not
allow the coexistence of CNAs that have embedded DCBX engines and CNAs
that do not, or even just retrieving DCB parameters by VF drivers.

The last patch adds an implementation of the dcbnl operations in their
proposed new semantics to the bnx2x, allowing users to configure and
manage the embedded DCBX engine.

The entire patch series is dependent on the following patches:
[net-next-2.6 PATCH 1/3] dcbnl: add support for ieee8021Qaz attributes
[net-next-2.6 PATCH 2/3] dcbnl: add appliction tlv handlers
[net-next-2.6 PATCH 3/3] net_dcb: add application notifiers

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