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:   Mon, 18 May 2020 12:05:04 -0700
From:   Vinicius Costa Gomes <>
To:     David Miller <>,
Subject: Re: [next-queue RFC 0/4] ethtool: Add support for frame preemption


David Miller <> writes:

> From: Vladimir Oltean <>
> Date: Sun, 17 May 2020 00:03:39 +0300
>> As to why this doesn't go to tc but to ethtool: why would it go to tc?
> Maybe you can't %100 duplicate the on-the-wire special format and
> whatever, but the queueing behavior ABSOLUTELY you can emulate in
> software.

Just saying what Vladimir said in different words: the queueing behavior
is already implemented in software, by mqprio or taprio, for example.

That is to say, if we add frame preemption support to those qdiscs all
they will do is pass the information to the driver, and that's it. They
won't be able to use that information at all.

The mental model I have for this feature is that is more similar to the
segmentation offloads, energy efficient ethernet or auto-negotiation
than it is to a traffic shaper like CBS.

> And then you have the proper hooks added for HW offload which can
> do the on-the-wire stuff.
> That's how we do these things, not with bolted on ethtool stuff.


Powered by blists - more mailing lists