[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY5PR12MB4322C4FE356BDAEDD91E3917DCA20@BY5PR12MB4322.namprd12.prod.outlook.com>
Date: Wed, 20 Jan 2021 03:21:46 +0000
From: Parav Pandit <parav@...dia.com>
To: Jason Wang <jasowang@...hat.com>,
"Michael S. Tsirkin" <mst@...hat.com>
CC: "virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
Eli Cohen <elic@...dia.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Sean Mooney <smooney@...hat.com>
Subject: RE: [PATCH linux-next v3 6/6] vdpa_sim_net: Add support for user
supported devices
> From: Jason Wang <jasowang@...hat.com>
> Sent: Tuesday, January 19, 2021 4:39 PM
> To: Parav Pandit <parav@...dia.com>; Michael S. Tsirkin <mst@...hat.com>
> Cc: virtualization@...ts.linux-foundation.org; Eli Cohen <elic@...dia.com>;
> netdev@...r.kernel.org; Sean Mooney <smooney@...hat.com>
> Subject: Re: [PATCH linux-next v3 6/6] vdpa_sim_net: Add support for user
> supported devices
>
>
> On 2021/1/15 下午2:27, Parav Pandit wrote:
> >>> With that mac, mtu as optional input fields provide the necessary
> >>> flexibility
> >> for different stacks to take appropriate shape as they desire.
> >>
> >>
> >> Thanks for the clarification. I think we'd better document the above
> >> in the patch that introduces the mac setting from management API.
> > Yes. Will do.
> > Thanks.
>
>
> Adding Sean.
>
> Regarding to mac address setting. Do we plan to allow to modify mac
> address after the creation? It looks like Openstack wants this.
>
Mac address is exposed in the features so yes, it should be possible to modify it as part of features modify command. (in future).
User needs to make sure that device is not attached to vhost or higher layer stack when device configuration layout is modified.
> Sean may share more information on this.
>
> Thanks
Powered by blists - more mailing lists