From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by dpdk.org (Postfix) with ESMTP id 8FB3C9A81 for ; Thu, 9 Jul 2015 16:52:00 +0200 (CEST) Received: by iecuq6 with SMTP id uq6so178189650iec.2 for ; Thu, 09 Jul 2015 07:52:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=h1jBbys/JvhzzE8YiGXzewyNBlrydaif7pdCF6J6jYI=; b=BEMvhTWzrWpf1tyDVnOhiHV2RtCR3rTuPP2KtKw3mqUiOnzwmyCDNYlL4AJrPWc9cR VT79WqkBeziIE7iofUMqiO1qwgOD4OgIxN6qMtaEO9o9zc02Fns8/6zbK2Drv6CN4Kof DeLk8Qt437eEzZVjXI/2E2qROgnOqbwoIobSFCIPWfBC4D46mMfJ3lwF5eHkx94LE90j PDP173IfIGsjJi70rpsF1BZvDSqf+qDjOlU3jOITFXS0wbDgpTd9siy73/lbbpLgteJq +25Z9ud3ogn3i7NwuYTssZlRM4QgJim6RYCP5DmhoFO4tbV7j5+puv4CoEfi5Y+fDUZ4 1OTQ== MIME-Version: 1.0 X-Received: by 10.50.62.106 with SMTP id x10mr6915742igr.29.1436453519977; Thu, 09 Jul 2015 07:51:59 -0700 (PDT) Received: by 10.36.194.129 with HTTP; Thu, 9 Jul 2015 07:51:59 -0700 (PDT) In-Reply-To: <559E26FE.8000302@bisdn.de> References: <559E26FE.8000302@bisdn.de> Date: Thu, 9 Jul 2015 07:51:59 -0700 Message-ID: From: Gopakumar Choorakkot Edakkunni To: Marc Sune Content-Type: text/plain; charset=UTF-8 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jul 2015 14:52:01 -0000 Crash is just one example I called out, the other example is a hotfix update to the app which ends up gracefully restarting the app. Rgds, Gopa. On Thu, Jul 9, 2015 at 12:47 AM, Marc Sune wrote: > > > 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. > >