Hi Lu From: Lu, Wenzhuo, Tuesday, January 16, 2018 7:54 AM > Hi Matan, > > > > -----Original Message----- > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Matan Azrad > > Sent: Sunday, January 7, 2018 5:46 PM > > To: Thomas Monjalon <tho...@monjalon.net>; Gaetan Rivet > > <gaetan.ri...@6wind.com>; Wu, Jingjing <jingjing...@intel.com> > > Cc: dev@dpdk.org; Neil Horman <nhor...@tuxdriver.com>; Richardson, > > Bruce <bruce.richard...@intel.com>; Ananyev, Konstantin > > <konstantin.anan...@intel.com> > > Subject: [dpdk-dev] [PATCH v2 6/6] app/testpmd: adjust ethdev port > > ownership > > > > Testpmd should not use ethdev ports which are managed by other DPDK > > entities. > > > > Set Testpmd ownership to each port which is not used by other entity > > and prevent any usage of ethdev ports which are not owned by Testpmd. > Sorry I don't follow all the discussion as there's too much. So it may be a > silly > question.
No problem, I'm here for any question :) > Testpmd already has the parameter " --pci-whitelist" to only use the assigned > devices. It is an EAL parameter. No? just say to EAL which devices to create.. > When using this parameter, all the devices are owned by the current > APP. No, what's about vdev? vdevs may manage devices(even whitlist PCI devices) by themselves and want to prevent any app to use these devices(see fail-safe PMD). > So I don't know why need to set/check the ownership. > BTW, in this patch, seem all the change is for ownership checking. I don't > find > the setting code. Do I miss something? Yes, see in main function (the first FOREACH). Thanks, Matan.
