From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cindy Lu <lulu@redhat.com>
Cc: Parav Pandit <parav@nvidia.com>,
Dragos Tatulea <dtatulea@nvidia.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"sgarzare@redhat.com" <sgarzare@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] vdpa: support set mac address from vdpa tool
Date: Tue, 9 Jul 2024 08:41:53 -0400 [thread overview]
Message-ID: <20240709084109-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACLfguXk4qiw4efRGK4Gw8OZQ_PKw6j+GVQJCVtbyJ+hxOoE0Q@mail.gmail.com>
On Tue, Jul 09, 2024 at 02:19:19PM +0800, Cindy Lu wrote:
> On Tue, 9 Jul 2024 at 11:59, Parav Pandit <parav@nvidia.com> wrote:
> >
> > Hi Cindy,
> >
> > > From: Cindy Lu <lulu@redhat.com>
> > > Sent: Monday, July 8, 2024 12:17 PM
> > >
> > > Add support for setting the MAC address using the VDPA tool.
> > > This feature will allow setting the MAC address using the VDPA tool.
> > > For example, in vdpa_sim_net, the implementation sets the MAC address to
> > > the config space. However, for other drivers, they can implement their own
> > > function, not limited to the config space.
> > >
> > > Changelog v2
> > > - Changed the function name to prevent misunderstanding
> > > - Added check for blk device
> > > - Addressed the comments
> > > Changelog v3
> > > - Split the function of the net device from vdpa_nl_cmd_dev_attr_set_doit
> > > - Add a lock for the network device's dev_set_attr operation
> > > - Address the comments
> > >
> > > Cindy Lu (2):
> > > vdpa: support set mac address from vdpa tool
> > > vdpa_sim_net: Add the support of set mac address
> > >
> > > drivers/vdpa/vdpa.c | 81 ++++++++++++++++++++++++++++
> > > drivers/vdpa/vdpa_sim/vdpa_sim_net.c | 19 ++++++-
> > > include/linux/vdpa.h | 9 ++++
> > > include/uapi/linux/vdpa.h | 1 +
> > > 4 files changed, 109 insertions(+), 1 deletion(-)
> > >
> > > --
> > > 2.45.0
> >
> > Mlx5 device already allows setting the mac and mtu during the vdpa device creation time.
> > Once the vdpa device is created, it binds to vdpa bus and other driver vhost_vdpa etc bind to it.
> > So there was no good reason in the past to support explicit config after device add complicate the flow for synchronizing this.
> >
> > The user who wants a device with new attributes, as well destroy and recreate the vdpa device with new desired attributes.
> >
> > vdpa_sim_net can also be extended for similar way when adding the vdpa device.
> >
> > Have you considered using the existing tool and kernel in place since 2021?
> > Such as commit d8ca2fa5be1.
> >
> > An example of it is,
> > $ vdpa dev add name bar mgmtdev vdpasim_net mac 00:11:22:33:44:55 mtu 9000
> >
> Hi Parav
> Really thanks for your comments. The reason for adding this function
> is to support Kubevirt.
> the problem we meet is that kubevirt chooses one random vdpa device
> from the pool and we don't know which one it going to pick. That means
> we can't get to know the Mac address before it is created. So we plan
> to have this function to change the mac address after it is created
> Thanks
> cindy
Well you will need to change kubevirt to teach it to set
mac address, right?
--
MST
next prev parent reply other threads:[~2024-07-09 12:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 6:47 [PATCH v3 0/2] vdpa: support set mac address from vdpa tool Cindy Lu
2024-07-08 6:47 ` [PATCH v3 1/2] " Cindy Lu
2024-07-08 7:04 ` Jason Wang
2024-07-08 9:15 ` kernel test robot
2024-07-08 6:47 ` [PATCH v3 2/2] vdpa_sim_net: Add the support of set mac address Cindy Lu
2024-07-08 7:06 ` Jason Wang
2024-07-08 7:18 ` Cindy Lu
2024-07-08 8:01 ` Jason Wang
2024-07-09 3:59 ` [PATCH v3 0/2] vdpa: support set mac address from vdpa tool Parav Pandit
2024-07-09 6:19 ` Cindy Lu
2024-07-09 12:41 ` Michael S. Tsirkin [this message]
2024-07-10 3:05 ` Jason Wang
2024-07-10 3:44 ` Parav Pandit
2024-07-10 6:10 ` Michael S. Tsirkin
2024-07-10 9:46 ` Cindy Lu
2024-07-11 9:08 ` Leonardo Milleri
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=20240709084109-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dtatulea@nvidia.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=sgarzare@redhat.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).