netdev - [PATCH net-next 0/3] Add QCN support to the DCB NL layer

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]

Message-Id: <1425473468-25969-1-git-send-email-ogerlitz@mellanox.com>
Date:	Wed,  4 Mar 2015 14:51:05 +0200
From:	Or Gerlitz <ogerlitz@...lanox.com>
To:	"David S. Miller" <davem@...emloft.net>,
	John Fastabend <john.r.fastabend@...el.com>
Cc:	netdev@...r.kernel.org, Amir Vadai <amirv@...lanox.com>,
	Tal Alon <talal@...lanox.com>,
	Or Gerlitz <ogerlitz@...lanox.com>
Subject: [PATCH net-next 0/3] Add QCN support to the DCB NL layer

Hi Dave, John, all

This series from Shani Michaeli adds support for the IEEE QCN attribute 
to the kernel DCB NL stack, and implementation in the mlx4 driver which
programs the firmware according to the admin directives.

Or.

Shani Michaeli (3):
  net/dcb: Add IEEE QCN attribute
  net/mlx4_core: Add basic elements for QCN
  net/mlx4_en: Add QCN parameters and statistics handling

 drivers/net/ethernet/mellanox/mlx4/cmd.c       |    9 +
 drivers/net/ethernet/mellanox/mlx4/en_dcb_nl.c |  218 ++++++++++++++++++++++++
 drivers/net/ethernet/mellanox/mlx4/fw.c        |   13 ++-
 drivers/net/ethernet/mellanox/mlx4/mlx4_en.h   |    1 +
 include/linux/mlx4/cmd.h                       |   13 ++
 include/linux/mlx4/device.h                    |    3 +-
 include/net/dcbnl.h                            |    3 +
 include/uapi/linux/dcbnl.h                     |   66 +++++++
 net/dcb/dcbnl.c                                |   41 ++++-
 9 files changed, 361 insertions(+), 6 deletions(-)

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