Virtualization - Dec 2020 - [PATCH 0/7] Introduce vdpa management tool

> From: Jakub Kicinski <kuba at kernel.org>
> Sent: Wednesday, December 16, 2020 9:36 PM
> 
> On Wed, 16 Dec 2020 04:13:51 -0500 Michael S. Tsirkin wrote:
> > > > > 3. Why not use ioctl() interface?
> > > >
> > > > Obviously I'm gonna ask you - why can't you use
devlink?
> > > >
> > > This was considered.
> > > However it seems that extending devlink for vdpa specific stats,
devices,
> config sounds overloading devlink beyond its defined scope.
> >
> > kuba what's your thinking here? Should I merge this as is?
> 
> No objections from me if people familiar with VDPA like it.
I was too occupied with the recent work on subfunction series.
I wanted to change the "parentdev" to "mgmtdev" to make it
little more clear for vdpa management tool to see vdpa mgmt device and operate
on it.
What do you think? Should I revise v2 or its late?

On Wed, Dec 16, 2020 at 04:54:37PM +0000, Parav Pandit
wrote:
> > From: Jakub Kicinski <kuba at kernel.org>
> > Sent: Wednesday, December 16, 2020 9:36 PM
> > 
> > On Wed, 16 Dec 2020 04:13:51 -0500 Michael S. Tsirkin wrote:
> > > > > > 3. Why not use ioctl() interface?
> > > > >
> > > > > Obviously I'm gonna ask you - why can't you use
devlink?
> > > > >
> > > > This was considered.
> > > > However it seems that extending devlink for vdpa specific
stats, devices,
> > config sounds overloading devlink beyond its defined scope.
> > >
> > > kuba what's your thinking here? Should I merge this as is?
> > 
> > No objections from me if people familiar with VDPA like it.
> 
> I was too occupied with the recent work on subfunction series.
> I wanted to change the "parentdev" to "mgmtdev" to make
it little more clear for vdpa management tool to see vdpa mgmt device and
operate on it.
> What do you think? Should I revise v2 or its late?
I need a rebase anyway, so sure.

-- 
MST