netdev - Re: [PATCH v4 net-next 00/10] Configuring congestion watermarks on ocelot switch using devlink-sb

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: <20210113192552.7d06261d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Wed, 13 Jan 2021 19:25:52 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Vladimir Oltean <olteanv@...il.com>
Cc:     "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
        alexandre.belloni@...tlin.com, andrew@...n.ch,
        f.fainelli@...il.com, vivien.didelot@...il.com,
        alexandru.marginean@....com, claudiu.manoil@....com,
        xiaoliang.yang_1@....com, hongbo.wang@....com, jiri@...nulli.us,
        idosch@...sch.org, UNGLinuxDriver@...rochip.com
Subject: Re: [PATCH v4 net-next 00/10] Configuring congestion watermarks on
 ocelot switch using devlink-sb

On Mon, 11 Jan 2021 19:43:06 +0200 Vladimir Oltean wrote:
> In some applications, it is important to create resource reservations in
> the Ethernet switches, to prevent background traffic, or deliberate
> attacks, from inducing denial of service into the high-priority traffic.
> 
> These patches give the user some knobs to turn. The ocelot switches
> support per-port and per-port-tc reservations, on ingress and on egress.
> The resources that are monitored are packet buffers (in cells of 60
> bytes each) and frame references.
> 
> The frames that exceed the reservations can optionally consume from
> sharing watermarks which are not per-port but global across the switch.
> There are 10 sharing watermarks, 8 of them are per traffic class and 2
> are per drop priority.
> 
> I am configuring the hardware using the best of my knowledge, and mostly
> through trial and error. Same goes for devlink-sb integration. Feedback
> is welcome.

This no longer applies.