[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191120034839-mutt-send-email-mst@kernel.org>
Date: Wed, 20 Nov 2019 03:52:23 -0500
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Parav Pandit <parav@...lanox.com>
Cc: Jason Wang <jasowang@...hat.com>,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
Dave Ertman <david.m.ertman@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"nhorman@...hat.com" <nhorman@...hat.com>,
"sassmann@...hat.com" <sassmann@...hat.com>,
"jgg@...pe.ca" <jgg@...pe.ca>, Kiran Patil <kiran.patil@...el.com>,
Alex Williamson <alex.williamson@...hat.com>,
Tiwei Bie <tiwei.bie@...el.com>
Subject: Re: [net-next v2 1/1] virtual-bus: Implementation of Virtual Bus
On Wed, Nov 20, 2019 at 03:38:18AM +0000, Parav Pandit wrote:
>
>
> > From: Jason Wang <jasowang@...hat.com>
> > Sent: Tuesday, November 19, 2019 9:15 PM
> >
> > ----- Original Message -----
> > >
> > >
> > > > From: Jason Wang <jasowang@...hat.com>
> > > > 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
Powered by blists - more mailing lists