[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACGkMEtKFZwPpzjNBv2j6Y5L=jYTrW4B8FnSLRMWb_AtqqSSDQ@mail.gmail.com>
Date: Mon, 17 Jun 2024 09:48:17 +0800
From: Jason Wang <jasowang@...hat.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: Jakub Kicinski <kuba@...nel.org>, Cindy Lu <lulu@...hat.com>, dtatulea@...dia.com,
mst@...hat.com, virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org, netdev@...r.kernel.org,
Parav Pandit <parav@...dia.com>
Subject: Re: [PATCH 1/2] vdpa: support set mac address from vdpa tool
On Wed, Jun 12, 2024 at 2:30 PM Jiri Pirko <jiri@...nulli.us> wrote:
>
> Wed, Jun 12, 2024 at 03:58:10AM CEST, kuba@...nel.org wrote:
> >On Tue, 11 Jun 2024 13:32:32 +0800 Cindy Lu wrote:
> >> Add new UAPI to support the mac address from vdpa tool
> >> Function vdpa_nl_cmd_dev_config_set_doit() will get the
> >> MAC address from the vdpa tool and then set it to the device.
> >>
> >> The usage is: vdpa dev set name vdpa_name mac **:**:**:**:**:**
> >
> >Why don't you use devlink?
>
> Fair question. Why does vdpa-specific uapi even exist? To have
> driver-specific uapi Does not make any sense to me :/
It came with devlink first actually, but switched to a dedicated uAPI.
Parav(cced) may explain more here.
Thanks
>
Powered by blists - more mailing lists