From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stephen@networkplumber.org>
Received: from mail-pd0-f169.google.com (mail-pd0-f169.google.com
 [209.85.192.169]) by dpdk.org (Postfix) with ESMTP id 07303C35E
 for <dev@dpdk.org>; Thu,  9 Jul 2015 18:46:16 +0200 (CEST)
Received: by pdbep18 with SMTP id ep18so167979803pdb.1
 for <dev@dpdk.org>; Thu, 09 Jul 2015 09:46:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to
 :references:mime-version:content-type:content-transfer-encoding;
 bh=uN8e6QSYnU3N6E83bnjF1djD4S5RbNgKJ1Uc8Ow8hcw=;
 b=V0GVhI01dkme/sq0fJFf2ZVT2BKDoc6yzsBSK5hJQEQJssN2ZF/DT8KOHLx3gRJCHG
 zLcb/+nMlc84wfqC1lbkeannp+fbJ3tVbhwuXPHWGSWz9CGZBXNAP6NbR7zqHq7DJzRi
 YY4RmbgTtf8GpJC7feZYgSP25BnqpozJVLlZA/lPc36Vp8DfT0f+RvMt/hkn1z29WFXg
 X6uAdWqbBojP9uWFIHdGktQ0EamtGAWs/Zg23rPUAAl3/nQDc1OWnyhl6hkXrkwhtLP7
 JScc03DP29UjsWewGBr/EJhOnjh+taC6ag2If5POGfYUE2FT4Ni4pd2vEi5PnEgmvpM3
 O4QQ==
X-Gm-Message-State: ALoCoQl7h2ODlk8K8NIvjMiWWCIRJLgmd9u9Rx9EHan4grZov6XUmGtwxwqiiZxrvTPyW2qxLR89
X-Received: by 10.70.90.232 with SMTP id bz8mr32862632pdb.120.1436460375356;
 Thu, 09 Jul 2015 09:46:15 -0700 (PDT)
Received: from urahara (static-50-53-82-155.bvtn.or.frontiernet.net.
 [50.53.82.155])
 by smtp.gmail.com with ESMTPSA id g2sm6548589pdh.11.2015.07.09.09.46.14
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Thu, 09 Jul 2015 09:46:15 -0700 (PDT)
Date: Thu, 9 Jul 2015 09:46:24 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: Gopakumar Choorakkot Edakkunni <gopakumar.c.e@gmail.com>
Message-ID: <20150709094624.4788cc34@urahara>
In-Reply-To: <CABK1yFCWKH=OzGySgr+KqF71qcvCRNLHTirTqBCsZ+qj=jPbDg@mail.gmail.com>
References: <CABK1yFAvrovzvfyCROBNt-tNEbOYuYTh-G8FeHf4Js87jSBA2A@mail.gmail.com>
 <CABK1yFCWKH=OzGySgr+KqF71qcvCRNLHTirTqBCsZ+qj=jPbDg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] How to prevent KNI interface from getting deleted on
 application termination?
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jul 2015 16:46:16 -0000

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