netdev - Re: net: dsa: mv88e6xxx architecture

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

Message-Id: <DA0551C1-9EA6-416C-8515-1F47C3599B0B@padl.com>
Date: Sat, 21 Dec 2024 09:59:25 +1100
From: Luke Howard <lukeh@...l.com>
To: Vladimir Oltean <olteanv@...il.com>
Cc: netdev@...r.kernel.org, Andrew Lunn <andrew@...n.ch>,
        Kieran Tyrrell <kieran@...nda.com>, Max Hunter <max@...tershome.org>
Subject: Re: net: dsa: mv88e6xxx architecture


>> The catch is what to do with frames that share a priority with an AVB
>> class but are not negotiated by SRP. These frames could crowd out
>> frames from AVB streams. Marvell’s solution is a flag in the ATU which
>> indicates that the DA was added by SRP.
> 
> Can you please state in a vendor-agnostic way what does the switch do
> with that information, how does it treat those streams specially?

Frames that are part of a stream (as identified by DA, VID and PCP) egress through designated priority queues.

Frames that are not part of a stream, but otherwise have a matching priority, can be discarded or have their priority remarked.