[dpdk-dev] [PATCH 2.3] tools/dpdk_nic_bind.py: Verbosely warn the user on bind

2016-01-26 21:21, David Marchand: > On Tue, Jan 26, 2016 at 9:14 PM, Thomas Monjalon > wrote: > > 2015-12-11 11:20, Aaron Conole: > >> DPDK ports are only detected during the EAL initialization. After that, any > >> new DPDK ports which are bound will not be visible to the application. > >> > >> T

[dpdk-dev] [PATCH 2.3] tools/dpdk_nic_bind.py: Verbosely warn the user on bind

On Tue, Jan 26, 2016 at 9:14 PM, Thomas Monjalon wrote: > 2015-12-11 11:20, Aaron Conole: >> DPDK ports are only detected during the EAL initialization. After that, any >> new DPDK ports which are bound will not be visible to the application. >> >> The dpdk_nic_bind.py can be a bit more helpful to

[dpdk-dev] [PATCH 2.3] tools/dpdk_nic_bind.py: Verbosely warn the user on bind

2015-12-11 11:20, Aaron Conole: > DPDK ports are only detected during the EAL initialization. After that, any > new DPDK ports which are bound will not be visible to the application. > > The dpdk_nic_bind.py can be a bit more helpful to let users know that DPDK > enabled applications will not find

[dpdk-dev] [PATCH 2.3] tools/dpdk_nic_bind.py: Verbosely warn the user on bind

Ping... This patch has been sitting^Hrotting for a bit over a month. > DPDK ports are only detected during the EAL initialization. After that, any > new DPDK ports which are bound will not be visible to the application. > > The dpdk_nic_bind.py can be a bit more helpful to let users know that DPDK

[dpdk-dev] [PATCH 2.3] tools/dpdk_nic_bind.py: Verbosely warn the user on bind

DPDK ports are only detected during the EAL initialization. After that, any new DPDK ports which are bound will not be visible to the application. The dpdk_nic_bind.py can be a bit more helpful to let users know that DPDK enabled applications will not find rebound ports until after they have been