From: Jakub Kicinski <kuba@kernel.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Leon Romanovsky <leonro@nvidia.com>,
Dima Chumak <dchumak@nvidia.com>, Jiri Pirko <jiri@resnulli.us>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
Saeed Mahameed <saeedm@nvidia.com>,
Steffen Klassert <steffen.klassert@secunet.com>,
Simon Horman <simon.horman@corigine.com>
Subject: Re: [PATCH net-next v3 0/8] devlink: Add port function attributes
Date: Thu, 17 Aug 2023 20:07:25 -0700 [thread overview]
Message-ID: <20230817200725.20589529@kernel.org> (raw)
In-Reply-To: <cover.1692262560.git.leonro@nvidia.com>
On Thu, 17 Aug 2023 12:11:22 +0300 Leon Romanovsky wrote:
> Introduce hypervisor-level control knobs to set the functionality of PCI
> VF devices passed through to guests. The administrator of a hypervisor
> host may choose to change the settings of a port function from the
> defaults configured by the device firmware.
>
> The software stack has two types of IPsec offload - crypto and packet.
> Specifically, the ip xfrm command has sub-commands for "state" and
> "policy" that have an "offload" parameter. With ip xfrm state, both
> crypto and packet offload types are supported, while ip xfrm policy can
> only be offloaded in packet mode.
>
> The series introduces two new boolean attributes of a port function:
> ipsec_crypto and ipsec_packet. The goal is to provide a similar level of
> granularity for controlling VF IPsec offload capabilities, which would
> be aligned with the software model. This will allow users to decide if
> they want both types of offload enabled for a VF, just one of them, or
> none at all (which is the default).
>
> At a high level, the difference between the two knobs is that with
> ipsec_crypto, only XFRM state can be offloaded. Specifically, only the
> crypto operation (Encrypt/Decrypt) is offloaded. With ipsec_packet, both
> XFRM state and policy can be offloaded. Furthermore, in addition to
> crypto operation offload, IPsec encapsulation is also offloaded. For
> XFRM state, choosing between crypto and packet offload types is
> possible. From the HW perspective, different resources may be required
> for each offload type.
What's going on with all the outstanding nVidia patches?!
The expectation is 1 series per vendor / driver. Let's say
2 if there are core changes. You had 5 outstanding today.
I'm tossing this out.
--
pw-bot: defer
next prev parent reply other threads:[~2023-08-18 3:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 9:11 [PATCH net-next v3 0/8] devlink: Add port function attributes Leon Romanovsky
2023-08-17 9:11 ` [PATCH net-next v3 1/8] devlink: Expose port function commands to control IPsec crypto offloads Leon Romanovsky
2023-08-17 9:11 ` [PATCH net-next v3 2/8] devlink: Expose port function commands to control IPsec packet offloads Leon Romanovsky
2023-08-17 9:11 ` [PATCH net-next v3 3/8] net/mlx5: Drop extra layer of locks in IPsec Leon Romanovsky
2023-08-17 9:11 ` [PATCH net-next v3 4/8] net/mlx5e: Rewrite IPsec vs. TC block interface Leon Romanovsky
2023-08-17 9:11 ` [PATCH net-next v3 5/8] net/mlx5: Add IFC bits to support IPsec enable/disable Leon Romanovsky
2023-08-17 9:11 ` [PATCH net-next v3 6/8] net/mlx5: Provide an interface to block change of IPsec capabilities Leon Romanovsky
2023-08-17 9:11 ` [PATCH net-next v3 7/8] net/mlx5: Implement devlink port function cmds to control ipsec_crypto Leon Romanovsky
2023-08-17 9:11 ` [PATCH net-next v3 8/8] net/mlx5: Implement devlink port function cmds to control ipsec_packet Leon Romanovsky
2023-08-18 3:07 ` Jakub Kicinski [this message]
2023-08-18 4:19 ` [PATCH net-next v3 0/8] devlink: Add port function attributes Leon Romanovsky
2023-08-18 16:38 ` Jakub Kicinski
2023-08-18 18:36 ` Leon Romanovsky
2023-08-18 21:32 ` Jakub Kicinski
2023-08-21 20:41 ` Saeed Mahameed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230817200725.20589529@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dchumak@nvidia.com \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=simon.horman@corigine.com \
--cc=steffen.klassert@secunet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).