Subject: Re: [net-next v2 1/1] virtual-bus: Implementation of Virtual Bus

From: "Michael S. Tsirkin" <[email-masked]>
Date: Wed, 20 Nov 2019 03:52:23 -0500

On Wed, Nov 20, 2019 at 03:38:18AM +0000, Parav Pandit wrote:
> 
> 
> > From: Jason Wang <[email-masked]>
> > Sent: Tuesday, November 19, 2019 9:15 PM
> > 
> > ----- Original Message -----
> > >
> > >
> > > > From: Jason Wang <[email-masked]>
> > > > Sent: Tuesday, November 19, 2019 1:37 AM
> > > >
> > >
> > > Nop. Devlink is NOT net specific. It works at the bus/device level.
> > > Any block/scsi/crypto can register devlink instance and implement the
> > > necessary ops as long as device has bus.
> > >
> > 
> > Well, uapi/linux/devlink.h told me:
> > 
> > "
> >  * include/uapi/linux/devlink.h - Network physical device Netlink interface "
> > 
> > And the userspace tool was packaged into iproute2, the command was named
> > as "TC", "PORT", "ESWITCH". All of those were strong hints that it was network
> > specific. Even for networking, only few vendors choose to implement this.
> > 
> It is under iproute2 tool but it is not limited to networking.

Want to fix the documentation then?
That's sure to confuse people ...

-- 
MST