netdev - Re: ingress rate limiting on mv88e6xxx

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]

Date:   Mon, 30 Mar 2020 15:26:11 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     Rasmus Villemoes <rasmus.villemoes@...vas.dk>
Cc:     Network Development <netdev@...r.kernel.org>,
        Vivien Didelot <vivien.didelot@...il.com>,
        Florian Fainelli <f.fainelli@...il.com>
Subject: Re: ingress rate limiting on mv88e6xxx

On Mon, Mar 30, 2020 at 03:22:44PM +0200, Rasmus Villemoes wrote:
> I'm trying to figure out what the proper way is to expose the ingress
> rate limiting knobs of the mv88e6250 (and related) to userspace. The
> simpest seems to be a set of sysfs files for each port, but I'm assuming
> that's a no-go (?)
> 
> So what is the right way, and has anyone looked at hooking this up?

Hi Rasmus

You need to map TC to the switch QoS functions.

    Andrew