From: Marc Sune <marc.sune@bisdn.de>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] How to prevent KNI interface from getting deleted on application termination?
Date: Thu, 09 Jul 2015 09:47:10 +0200 [thread overview]
Message-ID: <559E26FE.8000302@bisdn.de> (raw)
In-Reply-To: <CABK1yFCWKH=OzGySgr+KqF71qcvCRNLHTirTqBCsZ+qj=jPbDg@mail.gmail.com>
On 09/07/15 08:36, Gopakumar Choorakkot Edakkunni 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
>
> Rgds,
> Gopa.
>
> On Wed, Jul 8, 2015 at 1:00 PM, Gopakumar Choorakkot Edakkunni
> <gopakumar.c.e@gmail.com> wrote:
>> 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.
Maybe a stupid question; why not fixing your application so that it
doesn't crash, instead of adding adhoc patches?
marc
>>
>> Any way to achieve that ? I just want to keep the KNI around even if
>> my app vanishes.
>>
>> Rgds,
>> Gopa.
next prev parent reply other threads:[~2015-07-09 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 20:00 Gopakumar Choorakkot Edakkunni
2015-07-09 6:36 ` Gopakumar Choorakkot Edakkunni
2015-07-09 7:47 ` Marc Sune [this message]
2015-07-09 14:51 ` Gopakumar Choorakkot Edakkunni
2015-07-09 16:46 ` Stephen Hemminger
2015-07-09 20:47 ` Gopakumar Choorakkot Edakkunni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=559E26FE.8000302@bisdn.de \
--to=marc.sune@bisdn.de \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).