From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH 2.3] tools/dpdk_nic_bind.py: Verbosely warn the user on bind Date: Tue, 26 Jan 2016 21:14:31 +0100 Message-ID: <2190233.dCyjSQMtc6@xps13> References: <1449850823-29017-1-git-send-email-aconole@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Aaron Conole , david.marchand@6wind.com Return-path: Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com [74.125.82.44]) by dpdk.org (Postfix) with ESMTP id 95E319386 for ; Tue, 26 Jan 2016 21:15:39 +0100 (CET) Received: by mail-wm0-f44.google.com with SMTP id r129so119852426wmr.0 for ; Tue, 26 Jan 2016 12:15:39 -0800 (PST) In-Reply-To: <1449850823-29017-1-git-send-email-aconole@redhat.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" 2015-12-11 11:20, Aaron Conole: > DPDK ports are only detected during the EAL initialization. After that, any > new DPDK ports which are bound will not be visible to the application. > > The dpdk_nic_bind.py can be a bit more helpful to let users know that DPDK > enabled applications will not find rebound ports until after they have been > restarted. I think it's better to improve hotplug and allow hot binding. A work is in progress towards this direction. David, can you confirm? Is this patch still valuable in the meantime? > --- a/tools/dpdk_nic_bind.py > +++ b/tools/dpdk_nic_bind.py > @@ -344,8 +344,10 @@ def bind_one(dev_id, driver, force): > dev["Driver_str"] = "" # clear driver string > > # if we are binding to one of DPDK drivers, add PCI id's to that driver > + bDpdkDriver = False Please do not use camel case.