On Thu, Jun 06, 2019 at 03:43:02PM +0800, Xiaoyun Li wrote: > In order to allow binding/unbinding of devices for use by the > ntb_rawdev, we need to update the devbind script to add a new class > of device, and add device ids for the specific HW instances. And > only support skx platform right now. > > Signed-off-by: Xiaoyun Li <xiaoyun...@intel.com> > --- > usertools/dpdk-devbind.py | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/usertools/dpdk-devbind.py b/usertools/dpdk-devbind.py > index 9e79f0d28..3f7eafe28 100755 > --- a/usertools/dpdk-devbind.py > +++ b/usertools/dpdk-devbind.py > @@ -36,11 +36,15 @@ > octeontx2_npa = {'Class': '08', 'Vendor': '177d', 'Device': 'a0fb,a0fc', > 'SVendor': None, 'SDevice': None} > > +intel_ntb_skx = {'Class': '06', 'Vendor': '8086', 'Device': '201c', > + 'SVendor': None, 'SDevice': None} > + > network_devices = [network_class, cavium_pkx, avp_vnic, ifpga_class] > crypto_devices = [encryption_class, intel_processor_class] > eventdev_devices = [cavium_sso, cavium_tim, octeontx2_sso] > mempool_devices = [cavium_fpa, octeontx2_npa] > compress_devices = [cavium_zip] > +communication_devices = [intel_ntb_skx] >
Looking at this patch, and my own rawdev set for adding the ioat driver, I wonder if it's really a good idea to add new categories for each rawdev device type. Given we don't know how many device types there will be overall, I wonder if it's better to just add a "misc" or "other" device type section, where we put all raw devices. /Bruce