netdev - Re: [PATCH net-next 0/8] mlxsw: Support DSCP prioritization and rewrite

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 27 Jul 2018 13:18:18 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     idosch@...lanox.com
Cc:     netdev@...r.kernel.org, jiri@...lanox.com, petrm@...lanox.com,
        mlxsw@...lanox.com, john.fastabend@...il.com
Subject: Re: [PATCH net-next 0/8] mlxsw: Support DSCP prioritization and
 rewrite

From: Ido Schimmel <idosch@...lanox.com>
Date: Fri, 27 Jul 2018 15:26:54 +0300

> Petr says:
> 
> On ingress, a network device such as a switch assigns to packets
> priority based on various criteria. Common options include interpreting
> PCP and DSCP fields according to user configuration. When a packet
> egresses the switch, a reverse process may rewrite PCP and/or DSCP
> headers according to packet priority.
> 
> So far, mlxsw has supported prioritization based on PCP (802.1p priority
> tag). This patch set introduces support for prioritization based on
> DSCP, and DSCP rewrite.
> 
> To configure the DSCP-to-priority maps, the user is expected to invoke
> ieee_setapp and ieee_delapp DCBNL ops, e.g. by using lldptool:
 ...
> With this patch set, mlxsw uses these values to configure priority for
> DSCP values not explicitly specified in DSCP APP map. In the future we
> expect to also use this to configure default port priority for untagged
> packets.
> 
> Access to DSCP-to-priority map, priority-to-DSCP map, and default
> priority for a port is exposed through three new DCB helpers. Like the
> already-existing dcb_ieee_getapp_mask() helper, these helpers operate in
> terms of bitmaps, to support the arbitrary M:N mapping that the APP
> rules allow. Such interface presents all the relevant information from
> the APP database without necessitating exposition of iterators, locking
> or other complex primitives. It is up to the driver to then digest the
> mapping in a way that the device supports. In this patch set, mlxsw
> resolves conflicts by favoring higher-numbered DSCP values and
> priorities.

Series applied, thank you!