From: Stephen Hemminger <stephen@networkplumber.org>
To: Gopakumar Choorakkot Edakkunni <gopakumar.c.e@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] How to prevent KNI interface from getting deleted on application termination?
Date: Thu, 9 Jul 2015 09:46:24 -0700 [thread overview]
Message-ID: <20150709094624.4788cc34@urahara> (raw)
In-Reply-To: <CABK1yFCWKH=OzGySgr+KqF71qcvCRNLHTirTqBCsZ+qj=jPbDg@mail.gmail.com>
On Wed, 8 Jul 2015 23:36:52 -0700
Gopakumar Choorakkot Edakkunni <gopakumar.c.e@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
next prev parent reply other threads:[~2015-07-09 16:46 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
2015-07-09 14:51 ` Gopakumar Choorakkot Edakkunni
2015-07-09 16:46 ` Stephen Hemminger [this message]
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=20150709094624.4788cc34@urahara \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=gopakumar.c.e@gmail.com \
/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).