From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: elic@nvidia.com, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH linux-next v3 0/6] vdpa: enable user to set mac, mtu
Date: Thu, 5 Aug 2021 05:57:42 -0400 [thread overview]
Message-ID: <20210805055623-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20210616191155.102303-1-parav@nvidia.com>
On Wed, Jun 16, 2021 at 10:11:49PM +0300, Parav Pandit wrote:
> Currently user cannot set the mac address and mtu of the vdpa device.
> This patchset enables users to set the mac address and mtu of the vdpa
> device once the device is created.
> If a vendor driver supports such configuration user can set it otherwise
> user gets unsupported error.
This makes sense to me overall. People are used to
use netlink to set these parameters, and virtio does
not necessarily have a way to set all device
parameters - they can be RO in the config space.
> vdpa mac address and mtu are device configuration layout fields.
> To keep interface generic enough for multiple types of vdpa devices, mac
> address and mtu setting is implemented as configuration layout config
> knobs.
> This enables to use similar config layout for other virtio devices.
>
> An example of query & set of config layout fields for vdpa_sim_net
> driver:
>
> Configuration layout fields are set after device is created.
> This enables user to change such fields at later point without destroying and
> recreating the device for new config.
>
> $ vdpa mgmtdev show
> vdpasim_net:
> supported_classes net
>
> Add the device:
> $ vdpa dev add name bar mgmtdev vdpasim_net
>
> Configure mac address and mtu:
> $ vdpa dev config set bar mac 00:11:22:33:44:55 mtu 9000
>
> In above command only mac address or only mtu can also be set.
>
> View the config after setting:
> $ vdpa dev config show
> bar: mac 00:11:22:33:44:55 link up link_announce false mtu 9000 speed 0 duplex 0
>
> Patch summary:
> Patch-1 introduced and use helpers for get/set config area
> Patch-2 implement query device config layout
> Patch-3 enanble user to set mac and mtu in config space
> Patch-4 vdpa_sim_net implements get and set of config layout
> Patch-5 mlx5 vdpa driver supports user provided mac config
> Patch-6 mlx5 vdpa driver uses user provided mac during rx flow steering
>
> changelog:
> v2->v3:
> - dropped patches which are merged
> - simplified code to handle non transitional devices
>
> v1->v2:
> - new patches to fix kdoc comment to add new kdoc section
> - new patch to have synchronized access to features and config space
> - read whole net config layout instead of individual fields
> - added error extack for unmanaged vdpa device
> - fixed several endianness issues
> - introduced vdpa device ops for get config which is synchronized
> with other get/set features ops and config ops
> - fixed mtu range checking for max
> - using NLA_POLICY_ETH_ADDR
> - set config moved to device ops instead of mgmtdev ops
> - merged build and set to single routine
> - ensuring that user has NET_ADMIN capability for configuring network
> attributes
> - using updated interface and callbacks for get/set config
> - following new api for config get/set for mgmt tool in mlx5 vdpa
> driver
> - fixes for accessing right SF dma device and bar address
> - fix for mtu calculation
> - fix for bit access in features
> - fix for index restore with suspend/resume operation
>
>
> Eli Cohen (2):
> vdpa/mlx5: Support configuration of MAC
> vdpa/mlx5: Forward only packets with allowed MAC address
>
> Parav Pandit (4):
> vdpa: Introduce and use vdpa device get, set config helpers
> vdpa: Introduce query of device config layout
> vdpa: Enable user to set mac and mtu of vdpa device
> vdpa_sim_net: Enable user to set mac address and mtu
>
> drivers/vdpa/mlx5/net/mlx5_vnet.c | 101 ++++++--
> drivers/vdpa/vdpa.c | 337 +++++++++++++++++++++++++++
> drivers/vdpa/vdpa_sim/vdpa_sim.c | 13 ++
> drivers/vdpa/vdpa_sim/vdpa_sim.h | 2 +
> drivers/vdpa/vdpa_sim/vdpa_sim_net.c | 34 +--
> drivers/vhost/vdpa.c | 3 +-
> include/linux/vdpa.h | 38 +--
> include/uapi/linux/vdpa.h | 12 +
> 8 files changed, 490 insertions(+), 50 deletions(-)
>
> --
> 2.26.2
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-08-05 9:57 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 19:11 [PATCH linux-next v3 0/6] vdpa: enable user to set mac, mtu Parav Pandit
2021-06-16 19:11 ` [PATCH linux-next v3 1/6] vdpa: Introduce and use vdpa device get, set config helpers Parav Pandit
2021-06-22 7:08 ` Jason Wang
2021-06-16 19:11 ` [PATCH linux-next v3 2/6] vdpa: Introduce query of device config layout Parav Pandit
2021-06-22 7:20 ` Jason Wang
2021-06-22 14:03 ` Parav Pandit
2021-06-23 4:08 ` Jason Wang
2021-06-23 4:22 ` Parav Pandit
2021-06-24 5:43 ` Jason Wang
2021-06-24 6:29 ` Parav Pandit
2021-06-24 7:05 ` Jason Wang
2021-06-24 7:59 ` Parav Pandit
2021-06-25 3:28 ` Jason Wang
2021-06-25 6:45 ` Parav Pandit
2021-06-28 5:03 ` Jason Wang
2021-06-28 10:56 ` Parav Pandit
2021-06-29 3:52 ` Jason Wang
2021-06-29 9:49 ` Parav Pandit
2021-06-30 4:31 ` Jason Wang
2021-06-30 6:03 ` Parav Pandit
2021-07-01 3:34 ` Jason Wang
2021-07-01 7:00 ` Parav Pandit
2021-07-01 7:43 ` Jason Wang
2021-07-02 6:04 ` Parav Pandit
2021-07-05 4:35 ` Jason Wang
2021-07-06 17:07 ` Parav Pandit
2021-07-07 4:03 ` Jason Wang
2021-06-28 22:39 ` Michael S. Tsirkin
2021-06-29 3:41 ` Jason Wang
2021-06-29 20:01 ` Michael S. Tsirkin
2021-06-30 3:46 ` Jason Wang
2021-06-16 19:11 ` [PATCH linux-next v3 3/6] vdpa: Enable user to set mac and mtu of vdpa device Parav Pandit
2021-06-22 7:43 ` Jason Wang
2021-06-22 14:09 ` Parav Pandit
2021-06-16 19:11 ` [PATCH linux-next v3 4/6] vdpa_sim_net: Enable user to set mac address and mtu Parav Pandit
2021-06-16 19:11 ` [PATCH linux-next v3 5/6] vdpa/mlx5: Support configuration of MAC Parav Pandit
2021-06-16 19:11 ` [PATCH linux-next v3 6/6] vdpa/mlx5: Forward only packets with allowed MAC address Parav Pandit
2021-08-05 9:57 ` Michael S. Tsirkin [this message]
2021-08-05 10:13 ` [PATCH linux-next v3 0/6] vdpa: enable user to set mac, mtu Parav Pandit via Virtualization
2021-08-05 12:05 ` Michael S. Tsirkin
2021-08-06 2:50 ` Jason Wang
2021-08-06 8:42 ` Michael S. Tsirkin
2021-08-06 8:55 ` Parav Pandit via Virtualization
2021-08-09 3:07 ` Jason Wang
2021-08-09 3:13 ` Parav Pandit via Virtualization
2021-08-09 3:29 ` Jason Wang
[not found] ` <20210809052121.GA209158@mtl-vdi-166.wap.labs.mlnx>
2021-08-09 5:42 ` Parav Pandit via Virtualization
[not found] ` <20210809055748.GA210406@mtl-vdi-166.wap.labs.mlnx>
2021-08-09 6:01 ` Parav Pandit via Virtualization
[not found] ` <20210809060746.GA210718@mtl-vdi-166.wap.labs.mlnx>
2021-08-09 6:10 ` Parav Pandit via Virtualization
2021-08-09 7:05 ` Jason Wang
2021-08-16 20:51 ` Michael S. Tsirkin
2021-08-09 9:40 ` Michael S. Tsirkin
2021-08-09 9:51 ` Parav Pandit via Virtualization
2021-08-16 20:54 ` Michael S. Tsirkin
2021-08-18 3:14 ` Parav Pandit via Virtualization
2021-08-18 4:31 ` Jason Wang
2021-08-18 4:36 ` Parav Pandit via Virtualization
2021-08-19 4:18 ` Jason Wang
2021-08-18 17:33 ` Michael S. Tsirkin
2021-08-19 4:22 ` Jason Wang
2021-08-19 5:23 ` Parav Pandit via Virtualization
2021-08-19 7:15 ` Jason Wang
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=20210805055623-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=elic@nvidia.com \
--cc=parav@nvidia.com \
--cc=virtualization@lists.linux-foundation.org \
/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).