On 3/30/2018 1:00 AM, Stephen Hemminger wrote:
On Fri, 30 Mar 2018 00:00:05 +0800 Jeff Guo <jia....@intel.com> wrote:Use testpmd for example, to show an application how to use device event mechanism to monitor the hotplug event, involve both hot removal event and the hot insertion event. The process is that, testpmd first enable hotplug monitoring and register the user's callback, when device being hotplug insertion or hotplug removal, the eal monitor the event and call user's callbacks, the application according their hot plug policy to detach or attach the device from the bus. Signed-off-by: Jeff Guo <jia....@intel.com> --- v17->v16: unregister all user's callback when stop event monitor --- app/test-pmd/parameters.c | 5 +- app/test-pmd/testpmd.c | 242 +++++++++++++++++++++++++++++++++++++++++++++- app/test-pmd/testpmd.h | 11 +++ 3 files changed, 256 insertions(+), 2 deletions(-) diff --git a/app/test-pmd/parameters.c b/app/test-pmd/parameters.c index 97d22b8..825d602 100644 --- a/app/test-pmd/parameters.c +++ b/app/test-pmd/parameters.c @@ -186,6 +186,7 @@ usage(char* progname) printf(" --flow-isolate-all: " "requests flow API isolated mode on all ports at initialization time.\n"); printf(" --tx-offloads=0xXXXXXXXX: hexadecimal bitmask of TX queue offloads\n"); + printf(" --hot-plug: enalbe hot plug for device.\n")s/enalbe/enable/
will correct it.
