From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: How to prevent KNI interface from getting deleted on application termination? Date: Thu, 9 Jul 2015 09:46:24 -0700 Message-ID: <20150709094624.4788cc34@urahara> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Gopakumar Choorakkot Edakkunni Return-path: 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 ; Thu, 9 Jul 2015 18:46:16 +0200 (CEST) Received: by pdbep18 with SMTP id ep18so167979803pdb.1 for ; Thu, 09 Jul 2015 09:46:15 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, 8 Jul 2015 23:36:52 -0700 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 I don't think it is that simple given the shared ring in KNI