From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: Permanently binding NIC ports with DPDK drivers Date: Wed, 11 Nov 2015 14:01:21 -0500 Message-ID: <20151111190121.GB18270@mhcomputing.net> References: <964049bfb9054699a2e4520c6758a7ee@bilemail1.empirix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev@dpdk.org" To: "Montorsi, Francesco" Return-path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170]) by dpdk.org (Postfix) with ESMTP id ECE9E8DA9 for ; Wed, 11 Nov 2015 20:01:21 +0100 (CET) Content-Disposition: inline In-Reply-To: <964049bfb9054699a2e4520c6758a7ee@bilemail1.empirix.com> 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" In my development environment I set up an at-boot provisioning script that does it. I recommend using scripts and not shelling out from C code. ;) On Wed, Nov 11, 2015 at 04:13:01PM +0000, Montorsi, Francesco wrote: > Hi, > Is there a way to permanently (i.e., have the configuration automatically applied after reboot) bind a NIC port to DPDK? > > In case there's none, I'm thinking to save in my software a list of the NIC ports chosen by the user for use with DPDK and then, upon software startup to just do > for (int i=0; i < ...; i++) > system("dpdk_nic_bind.py --bind=igb_uio " + PCI_device_chosen[i]); > Do you see any problem with that? > > Thanks! > Francesco Montorsi >