On 10/19/2018 1:23 AM, Dan Gora wrote: > Update KNI example to add the command line flag '-m' to enable > a function to continuously monitor the Ethernet link status of > the physical link and update the link status of the corresponding > interfaces with rte_kni_update_link(). > > Signed-off-by: Dan Gora <d...@adax.com>
<...> > +Running the kni Example Application > +----------------------------------- > > -Loading the KNI kernel module without any parameter is the typical way a > DPDK application > -gets packets into and out of the kernel net stack. > -This way, only one kernel thread is created for all KNI devices for packet > receiving in kernel side: > +The ``kni`` example application requires a number of command line options: > > .. code-block:: console > > - #insmod rte_kni.ko > + kni [EAL options] -- -P -p PORTMASK > --config="(port,lcore_rx,lcore_tx[,lcore_kthread,...])[,(port,lcore_rx,lcore_tx[,lcore_kthread,...])]" + [-m]: kni [EAL options] -- -P -p PORTMASK --config="(port,lcore_rx,lcore_tx[,lcore_kthread,...])[,(port,lcore_rx,lcore_tx[,lcore_kthread,...])]" [-m] Can be added while merging. <...> > - > -Callbacks for Kernel Requests > -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > - > -To execute specific PMD operations in user space requested by some Linux* > commands, > -callbacks must be implemented and filled in the struct rte_kni_ops structure. > -Currently, setting a new MTU, change in MAC address, configuring > promiscusous mode and > -configuring the network interface(up/down) re supported. > -Default implementation for following is available in rte_kni library. > -Application may choose to not implement following callbacks: > - > -- ``config_mac_address`` > -- ``config_promiscusity`` I am for keeping this section, is there any specific reason to remove this?
