> From: Virtualization <virtualization-bounces@xxxxxxxxxxxxxxxxxxxxxxxxxx> On > Behalf Of Parav Pandit > > > From: Jason Wang <jasowang@xxxxxxxxxx> > > Sent: Tuesday, January 19, 2021 4:39 PM > > To: Parav Pandit <parav@xxxxxxxxxx>; Michael S. Tsirkin > > <mst@xxxxxxxxxx> > > Cc: virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx; Eli Cohen > > <elic@xxxxxxxxxx>; netdev@xxxxxxxxxxxxxxx; Sean Mooney > > <smooney@xxxxxxxxxx> > > 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. > Just curious, why Openstack cannot set the mac address at device creation time? Is vdpa device created by non Openstack software? Does it always want to set the mac address of vdpa device? > > Sean may share more information on this. _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
