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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240308201435.2790b7b4@kernel.org>
Date: Fri, 8 Mar 2024 20:14:35 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: William Tu <witu@...dia.com>
Cc: <netdev@...r.kernel.org>, <jiri@...dia.com>, <bodong@...dia.com>
Subject: Re: [PATCH net-next] Documentation: Add documentation for eswitch
 attribute

On Fri, 8 Mar 2024 02:01:06 +0200 William Tu wrote:
> +   * - ``mode``
> +     - enum
> +     - The mode of the device. The mode can be one of the following:
> +
> +       * ``legacy`` Legacy SRIOV.
> +       * ``switchdev`` SRIOV switchdev offloads.

In my head `mode` is special because it controls on / off for
switchdev, and none of the other attrs do anything outside of
switchdev mode. But thinking about it now, I'm not sure if that's
actually the case. Let's clarify. And if other attrs indeed are
only meaningful in switchdev mode we should feature `mode` more
prominently than others. Separate section perhaps?

Please link to representors.rst and perhaps switchdev.rst ?
-- 
pw-bot: cr

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ