netdev - Re: [PATCH net-next 0/3] mlxsw: Allow setting default port priority

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

Message-Id: <20200102.154034.2123269473192368005.davem@davemloft.net>
Date:   Thu, 02 Jan 2020 15:40:34 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     idosch@...sch.org
Cc:     netdev@...r.kernel.org, jiri@...lanox.com, petrm@...lanox.com,
        mlxsw@...lanox.com, idosch@...lanox.com
Subject: Re: [PATCH net-next 0/3] mlxsw: Allow setting default port priority

From: Ido Schimmel <idosch@...sch.org>
Date: Sun, 29 Dec 2019 13:48:26 +0200

> From: Ido Schimmel <idosch@...lanox.com>
> 
> Petr says:
> 
> When LLDP APP TLV selector 1 (EtherType) is used with PID of 0, the
> corresponding entry specifies "default application priority [...] when
> application priority is not otherwise specified."
> 
> mlxsw currently supports this type of APP entry, but uses it only as a
> fallback for unspecified DSCP rules. However non-IP traffic is prioritized
> according to port-default priority, not according to the DSCP-to-prio
> tables, and thus it's currently not possible to prioritize such traffic
> correctly.
> 
> This patchset extends the use of the abovementioned APP entry to also set
> default port priority (in patches #1 and #2) and then (in patch #3) adds a
> selftest.

Series applied, thanks Ido.

Always nice to see those test cases.