[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZmlAYcRHMqCgYBJD@nanopsycho.orion>
Date: Wed, 12 Jun 2024 08:29:53 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Cindy Lu <lulu@...hat.com>, dtatulea@...dia.com, mst@...hat.com,
jasowang@...hat.com, virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] vdpa: support set mac address from vdpa tool
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 :/
Powered by blists - more mailing lists