From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com [209.85.223.175]) by dpdk.org (Postfix) with ESMTP id 00ED2569A for ; Thu, 9 Jul 2015 08:36:53 +0200 (CEST) Received: by iecvh10 with SMTP id vh10so170847933iec.3 for ; Wed, 08 Jul 2015 23:36:52 -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 :content-type; bh=OqGtzhAlVAhAZ+/Z0HZhdvcziBRUMpJS6ekg2tvZgxo=; b=qqEiD8yI6LKzSltLqKngvvhX5bO8L7FKbuOxQ8J/QH1/GHwgdhQxAMW8brK8n0wME9 UgEnx/S13B1MTq9cysiFt4yDga/6YmkMa14uzQTeK2LD53XFLGihYgW+cEMcVFzISf8H vZeLFr8xP7uJ3qrhKvF6wOWk9AiETM2shDhvyzayGQUkuhi8A8kXp/oPGnwwt5ucj/lh KiFBctCKYJr9I3oB+NfusevPQAfPXnsGzmJFd1r1BVbZKlHxFSXBuakUlBkjw+L9o0um CH+eR2Z1kFGyuP1cCXWcY4Y/MD8RAfkAGYWjCqsz+UUjqPxHVr+R/+vPI8YGwa7CALRF 0iYg== MIME-Version: 1.0 X-Received: by 10.50.129.2 with SMTP id ns2mr8757095igb.5.1436423812453; Wed, 08 Jul 2015 23:36:52 -0700 (PDT) Received: by 10.36.194.129 with HTTP; Wed, 8 Jul 2015 23:36:52 -0700 (PDT) In-Reply-To: References: Date: Wed, 8 Jul 2015 23:36:52 -0700 Message-ID: From: Gopakumar Choorakkot Edakkunni To: dev@dpdk.org Content-Type: text/plain; charset=UTF-8 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 06:36:53 -0000 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. > > Any way to achieve that ? I just want to keep the KNI around even if > my app vanishes. > > Rgds, > Gopa.