You are right, I dint think of the rings. I guess if I keep the netdev intact and release the rings and stuff as it does on a /dev/kni close, that should be fine ? And when my app comes back up and opens dev/kni, the rings etc.. can be recreated, and when my app tries to create the netdevs, it reattaches it to the existing ones. The way I look at it, its similar to the tun/tap ioctl option TUNSETPERSIST.
Rgds, Gopa. On Thu, Jul 9, 2015 at 9:46 AM, Stephen Hemminger <stephen at networkplumber.org> wrote: > On Wed, 8 Jul 2015 23:36:52 -0700 > Gopakumar Choorakkot Edakkunni <gopakumar.c.e at gmail.com> wrote: > >> Reading through the KNI module source, doesnt look like there is a way >> to do this. For my requirement, I will make some patch tomorrow to >> have a module option to just keep the KNI data structures around even >> if /dev/kni is closed, looks straightforward to do from the code > > > I don't think it is that simple given the shared ring in KNI
