netdev - [PATCH net-next 0/3] dcbnl: Extending dcbnl to support HW based 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>] [day] [month] [year] [list]

Date:	Tue, 21 Dec 2010 21:32:35 +0200
From:	"Shmulik Ravid" <shmulikr@...adcom.com>
To:	davem@...emloft.net
cc:	eilong@...adcom.com, lucy.liu@...el.com, netdev@...r.kernel.org
Subject: [PATCH net-next 0/3] dcbnl: Extending dcbnl to support HW based
 DCBX

DCBX is the exchange protocol for negotiating DCB parameters between a
host and a switch. Many converged network adapters support an embedded
DCBX engine that performs the negotiation and configures the device
with the negotiated parameters. The following patches extend the dcbnl
netlink interface so in addition to its current semantics it offers a
standard mechanism for managing such embedded 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 allows a user to configure the device
with the negotiated parameters only after the negotiation itself is
performed by an external entity (such as lldpad). As DCBX runs on top
of LLDP, there can be only one entity responsible for the negotiation
for each physical port. Thus the current scheme does not allow the
coexistence of CNAs that have embedded DCBX engines and CNAs that do
not.

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.

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