From: Leon Romanovsky <leon@kernel.org>
To: Gautam Dawar <gautam.dawar@amd.com>, Jakub Kicinski <kuba@kernel.org>
Cc: linux-net-drivers@amd.com, jasowang@redhat.com,
Edward Cree <ecree.xilinx@gmail.com>,
Martin Habets <habetsm.xilinx@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
eperezma@redhat.com, harpreet.anand@amd.com, tanuj.kamde@amd.com,
koushik.dutta@amd.com
Subject: Re: [PATCH net-next v4 00/14] sfc: add vDPA support for EF100 devices
Date: Sun, 9 Apr 2023 12:13:25 +0300 [thread overview]
Message-ID: <20230409091325.GF14869@unreal> (raw)
In-Reply-To: <20230407081021.30952-1-gautam.dawar@amd.com>
On Fri, Apr 07, 2023 at 01:40:01PM +0530, Gautam Dawar wrote:
> Hi All,
>
> This series adds the vdpa support for EF100 devices.
> For now, only a network class of vdpa device is supported and
> they can be created only on a VF. Each EF100 VF can have one
> of the three function personalities (EF100, vDPA & None) at
> any time with EF100 being the default. A VF's function personality
> is changed to vDPA while creating the vdpa device using vdpa tool.
Jakub,
I wonder if it is not different approach to something that other drivers
already do with devlink enable knobs (DEVLINK_PARAM_GENERIC_ID_ENABLE_*)
and auxiliary bus.
Thanks
next prev parent reply other threads:[~2023-04-09 9:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 8:10 [PATCH net-next v4 00/14] sfc: add vDPA support for EF100 devices Gautam Dawar
2023-04-07 8:10 ` [PATCH net-next v4 01/14] sfc: add function personality " Gautam Dawar
2023-04-07 8:10 ` [PATCH net-next v4 02/14] sfc: implement MCDI interface for vDPA operations Gautam Dawar
2023-04-10 9:54 ` Simon Horman
2023-04-07 8:10 ` [PATCH net-next v4 03/14] sfc: update MCDI headers for CLIENT_CMD_VF_PROXY capability bit Gautam Dawar
2023-04-07 8:10 ` [PATCH net-next v4 04/14] sfc: evaluate vdpa support based on FW capability CLIENT_CMD_VF_PROXY Gautam Dawar
2023-04-07 8:10 ` [PATCH net-next v4 05/14] sfc: implement init and fini functions for vDPA personality Gautam Dawar
2023-04-07 8:10 ` [PATCH net-next v4 06/14] sfc: implement vDPA management device operations Gautam Dawar
2023-04-10 10:22 ` Simon Horman
2023-04-07 8:10 ` [PATCH net-next v4 07/14] sfc: implement vdpa device config operations Gautam Dawar
2023-04-07 8:10 ` [PATCH net-next v4 08/14] sfc: implement vdpa vring " Gautam Dawar
2023-04-10 12:48 ` Simon Horman
2023-04-07 8:10 ` [PATCH net-next v4 09/14] sfc: implement device status related vdpa " Gautam Dawar
2023-04-08 3:20 ` Jakub Kicinski
2023-04-10 6:23 ` Gautam Dawar
2023-04-10 12:47 ` Simon Horman
2023-04-07 8:10 ` [PATCH net-next v4 10/14] sfc: implement filters for receiving traffic Gautam Dawar
2023-04-08 3:21 ` Jakub Kicinski
2023-04-10 6:25 ` Gautam Dawar
2023-04-07 8:10 ` [PATCH net-next v4 11/14] sfc: use PF's IOMMU domain for running VF's MCDI commands Gautam Dawar
2023-04-07 8:10 ` [PATCH net-next v4 12/14] sfc: unmap VF's MCDI buffer when switching to vDPA mode Gautam Dawar
2023-04-07 8:10 ` [PATCH net-next v4 13/14] sfc: update vdpa device MAC address Gautam Dawar
2023-04-07 8:10 ` [PATCH net-next v4 14/14] sfc: register the vDPA device Gautam Dawar
2023-04-09 9:13 ` Leon Romanovsky [this message]
2023-04-10 1:39 ` [PATCH net-next v4 00/14] sfc: add vDPA support for EF100 devices Jason Wang
2023-04-10 6:33 ` Gautam Dawar
2023-04-10 7:53 ` Leon Romanovsky
2023-04-24 15:46 ` Martin Habets
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=20230409091325.GF14869@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=gautam.dawar@amd.com \
--cc=habetsm.xilinx@gmail.com \
--cc=harpreet.anand@amd.com \
--cc=jasowang@redhat.com \
--cc=koushik.dutta@amd.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=tanuj.kamde@amd.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).