From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx.bisdn.de (mx.bisdn.de [185.27.182.31]) by dpdk.org (Postfix) with ESMTP id 42F265A65 for ; Thu, 9 Jul 2015 09:47:12 +0200 (CEST) Received: from [192.168.1.40] (65.Red-88-20-102.staticIP.rima-tde.net [88.20.102.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx.bisdn.de (Postfix) with ESMTPSA id D1DBCA34B1 for ; Thu, 9 Jul 2015 09:47:11 +0200 (CEST) Message-ID: <559E26FE.8000302@bisdn.de> Date: Thu, 09 Jul 2015 09:47:10 +0200 From: Marc Sune User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: dev@dpdk.org References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jul 2015 07:47:12 -0000 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 > 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.