On 7/18/2019 6:27 AM, Nithin Kumar Dabilpuram wrote: > Hi Ferruh, > > On 7/17/2019 10:21 PM, Ferruh Yigit wrote: >> External Email >> >> ---------------------------------------------------------------------- >> On 7/17/2019 1:30 PM, Nithin Dabilpuram wrote: >>> With the latest published interface of >>> rte_eal_hotplug_[add,remove](), and rte_eth_dev_close(), >>> rte_eth_dev_close() would cleanup all the data structures of >>> port's eth dev leaving the device common resource intact >>> if RTE_ETH_DEV_CLOSE_REMOVE is set in dev flags. >>> >>> So a new command "detach device" (~hotplug remove) to work, >>> with device identifier like "port attach" is added >>> to be able to detach closed devices. >>> >>> Also to display currently probed devices, another command >>> "show device info <identifier>|all" is also added as a >>> part of this change. >> In "show device info all" output [1] there are 'dpaa' & 'fslmc' logs [2], do >> you >> know why we are getting them, can we get rid of them? >> > Is this issue sill there ? I'm not able to see it in my setup.
Yes, still there. I can see them with latest next-net. > >> >> >> [1] >> " >> ********************* Infos for device net_null0 ********************* >> Bus name: vdev >> Driver name: net_null >> Devargs: >> Connect to socket: 0 >> >> Port id: 1 >> MAC address: 8A:D0:A1:F3:B5:0C >> Device name: net_null0 >> dpaa: Invalid device string () >> >> fslmc: Invalid device string () >> " >> >> >> [2] >> " >> dpaa: Invalid device string () >> >> fslmc: Invalid device string () >> "
