[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0a1ed293-c709-eb93-f534-88d11e450a5f@kernel.org>
Date: Tue, 3 Oct 2023 08:46:51 -0600
From: David Ahern <dsahern@...nel.org>
To: Tariq Toukan <tariqt@...dia.com>,
Stephen Hemminger <stephen@...workplumber.org>
Cc: "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Jiri Pirko <jiri@...dia.com>, Dima Chumak <dchumak@...dia.com>,
Jakub Kicinski <kuba@...nel.org>, Leon Romanovsky <leonro@...dia.com>,
Saeed Mahameed <saeedm@...dia.com>, netdev@...r.kernel.org
Subject: Re: [PATCH iproute2-next V3 1/2] devlink: Support setting port
function ipsec_crypto cap
On 10/2/23 4:43 AM, Tariq Toukan wrote:
> From: Dima Chumak <dchumak@...dia.com>
>
> Support port function commands to enable / disable IPsec crypto
> offloads, this is used to control the port IPsec device capabilities.
>
> When IPsec crypto capability is disabled for a function of the port
> (default), function cannot offload IPsec operation. When enabled, IPsec
> operation can be offloaded by the function of the port.
>
> Enabling IPsec crypto offloads lets the kernel to delegate XFRM state
> processing and encrypt/decrypt operation to the device hardware.
>
> Example of a PCI VF port which supports IPsec crypto offloads:
>
> $ devlink port show pci/0000:06:00.0/1
> pci/0000:06:00.0/1: type eth netdev enp6s0pf0vf0 flavour pcivf pfnum 0 vfnum 0
> function:
> hw_addr 00:00:00:00:00:00 roce enable ipsec_crypto disable
>
> $ devlink port function set pci/0000:06:00.0/1 ipsec_crypto enable
>
> $ devlink port show pci/0000:06:00.0/1
> pci/0000:06:00.0/1: type eth netdev enp6s0pf0vf0 flavour pcivf pfnum 0 vfnum 0
> function:
> hw_addr 00:00:00:00:00:00 roce enable ipsec_crypto enable
>
Why not just 'ipsec' instead of 'ipsec_crypto'? What value does the
extra '_crypto' provide?
Powered by blists - more mailing lists