netdev - Re: [PATCH net-next V7 0/8] net/mlx4

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: <20120405.052828.1474884969422039237.davem@davemloft.net>
Date:	Thu, 05 Apr 2012 05:28:28 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	amirv@...lanox.com
Cc:	netdev@...r.kernel.org, roland@...estorage.com,
	yevgenyp@...lanox.com, oren@...lanox.com, amirv@....mellanox.co.il,
	john.r.fastabend@...el.com, eric.dumazet@...il.com
Subject: Re: [PATCH net-next V7 0/8] net/mlx4_en: DCB QoS support

From: Amir Vadai <amirv@...lanox.com>
Date: Thu,  5 Apr 2012 10:33:23 +0300

> DCBX version 802.1qaz is supported.
> User Priority (UP) is set in QP context instead of in WQE (QP Work Queue
> Element), which means that all traffic from a queue will have the same UP.
> UP is also set for untagged traffic to be able to classify such traffic too.
> 
> Mapping from sk_prio to User Priority is done by sch_mqprio mapping. Although
> confusingly sch_mqprio maps sk_prio to something called TC, it is not related
> to DCBX's TC, and is interpreted by mlx4_en driver as UP.
> 
> User can set maximal BW for an ETS TC. This could be done by a new optional
> attribute added to DCB_ATTR_IEEE called DCBNL DCB_ATTR_IEEE_MAXRATE. It accept
> an array of 8 64 bits values, 1 for every ETS TC. Units are in Kbps.

All applied, thanks.

Please double check that all the new locations that reference
ip_tos2prio have a proper dependency on CONFIG_INET.

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