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
| ||
|
Message-ID: <20220829075342.5ztd5hf4sznl7req@lx-anielsen> Date: Mon, 29 Aug 2022 09:53:42 +0200 From: "Allan W. Nielsen" <Allan.Nielsen@...rochip.com> To: Jakub Kicinski <kuba@...nel.org> CC: Petr Machata <petrm@...dia.com>, <Daniel.Machon@...rochip.com>, <netdev@...r.kernel.org>, <vinicius.gomes@...el.com>, <vladimir.oltean@....com>, <thomas.petazzoni@...tlin.com>, <maxime.chevallier@...tlin.com>, <roopa@...dia.com> Subject: Re: Basic PCP/DEI-based queue classification Hi, On 24.08.2022 17:54, Jakub Kicinski wrote: >For an uneducated maintainer like myself, how do embedded people look >at DCB? Only place I've seen it used is in RDMA clusers. I suggested >to Vladimir to look at DCBNL for frame preemption because it's the only >existing API we have that's vaguely relevant to HW/prio control but he >ended up going with ethtool. >No preference here, just trying to map it out in my head. As I work toghether with Daniel, I'm biased. But I work a lot with embedded devices ;-) I think this feature belong in DCB simply because DCB already have the related configurations (like the default prio, priority-flow-control etc), and it will be more logical for the user to find the PCP mapping in the same place. I think that framepreemption should be in ethtool as it is partly defined in IEEE802.3 (the physical layer) and it is ethernet only technology. /Allan
Powered by blists - more mailing lists