From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Montorsi, Francesco" Subject: Re: Permanently binding NIC ports with DPDK drivers Date: Wed, 11 Nov 2015 16:59:14 +0000 Message-ID: <289cd55a3a7b498c974a083927fc81cc@bilemail1.empirix.com> References: <964049bfb9054699a2e4520c6758a7ee@bilemail1.empirix.com> <20151111162853.GA38496@bricha3-MOBL3> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" To: Bruce Richardson Return-path: Received: from bilemail1.empirix.com (bilemail1.empirix.com [208.67.76.245]) by dpdk.org (Postfix) with ESMTP id 881FA532D for ; Wed, 11 Nov 2015 17:59:27 +0100 (CET) In-Reply-To: <20151111162853.GA38496@bricha3-MOBL3> Content-Language: en-US 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" Hi Bruce, > -----Original Message----- > From: Bruce Richardson [mailto:bruce.richardson@intel.com] > I'm not aware of any way to make the bindings permanent across reboots. > What you have suggested will work, but there are probably better ways to > do the same thing. I agree... let's see if somebody else has suggestions :) In any case my idea is to make my software as much independent as possible = from troubles with future HW and future DPDK versions. A way to do that wou= ld be to leave all the bind steps and intelligence inside the dpdk_nic_bind= .py script and just use that (since it will be probably always up to date a= nd correct). My only concern is that (reading the python code) dpdk_nic_bin= d.py script does not return with an error code !=3D 0 if something bad happ= ens during binding... maybe it may be worth doing such a small change... Just my 2 cents, Francesco