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  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:   Tue, 25 Aug 2020 12:46:12 +0300
From:   Vladimir Oltean <>
To:     Vinicius Costa Gomes <>
Cc:     Kurt Kanzenbach <>, Andrew Lunn <>,
        Vivien Didelot <>,
        Florian Fainelli <>,
        "David S. Miller" <>,
        Jakub Kicinski <>,,
        Rob Herring <>,,
        Sebastian Andrzej Siewior <>,
        Richard Cochran <>,
        Kamil Alkhouri <>,
Subject: Re: [PATCH v3 5/8] net: dsa: hellcreek: Add TAPRIO offloading support

Hi Vinicius,

On Mon, Aug 24, 2020 at 04:45:50PM -0700, Vinicius Costa Gomes wrote:
> Kurt Kanzenbach <> writes:
> >
> > With TAPRIO traffic classes and the mapping to queues can be
> > configured. The switch can also map traffic classes. That sounded like a
> > good match to me.
> The only reason I could think that you would need this that *right now*
> taprio has pretty glaring oversight: that in the offload parameters each entry
> 'gate_mask' reference the "Traffic Class" (i.e. bit 0 is Traffic Class
> 0), and it really should be the HW queue.

Sorry, but could you please explain why having the gate_mask reference
the traffic classes is a glaring oversight, and how changing it would
help here?

Also, Kurt, could you please explain what the
To me, it appears that it's configuring ingress QoS classification on
the port (and the reason why this is strange to me is because you're
applying this configuration through an egress qdisc), but I want to make
sure I'm not misunderstanding.


Powered by blists - more mailing lists