Wed, Nov 20, 2019 at 09:52:23AM CET, mst@xxxxxxxxxx wrote: >On Wed, Nov 20, 2019 at 03:38:18AM +0000, Parav Pandit wrote: >> >> >> > From: Jason Wang <jasowang@xxxxxxxxxx> >> > Sent: Tuesday, November 19, 2019 9:15 PM >> > >> > ----- Original Message ----- >> > > >> > > >> > > > From: Jason Wang <jasowang@xxxxxxxxxx> >> > > > 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 ... Will do. > >-- >MST >
