[dpdk-dev] How to prevent KNI interface from getting deleted on application termination?

Gopakumar Choorakkot Edakkunni gopakumar.c.e at gmail.com
Wed Jul 8 22:00:37 CEST 2015


Hi all,

My application takes over one/multiple ethernet port(s) in a linux
system and creates KNI interfaces corresponding to them. So if there
was eth0 and eth1 in the non-dpdk mode, once I take over the ports
using dpdk, I create eth0 and eth1 KNI interfaces. As far as the linux
network managers are concerned, they dont really know about it (or
care I guess) - for example the dhcp client tries getting a dhcp
address over these KNI interfaces and succeeds.

Now if my application crashes, I dont want the entire network
management subsystem on linux and the hotplugs and this and that to
get alarmed and routes to vanish from the route table etc.. etc.. The
application will crash and come back up real quick, nothing needs to
change in that meantime.

Any way to achieve that ? I just want to keep the KNI around even if
my app vanishes.

Rgds,
Gopa.


More information about the dev mailing list