From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Marchand Subject: Re: [PATCH 2.3] tools/dpdk_nic_bind.py: Verbosely warn the user on bind Date: Tue, 26 Jan 2016 21:21:29 +0100 Message-ID: References: <1449850823-29017-1-git-send-email-aconole@redhat.com> <2190233.dCyjSQMtc6@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: "dev@dpdk.org" To: Thomas Monjalon Return-path: Received: from mail-oi0-f47.google.com (mail-oi0-f47.google.com [209.85.218.47]) by dpdk.org (Postfix) with ESMTP id 3BD8E9388 for ; Tue, 26 Jan 2016 21:21:49 +0100 (CET) Received: by mail-oi0-f47.google.com with SMTP id r14so9328997oie.0 for ; Tue, 26 Jan 2016 12:21:49 -0800 (PST) In-Reply-To: <2190233.dCyjSQMtc6@xps13> 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" On Tue, Jan 26, 2016 at 9:14 PM, Thomas Monjalon wrote: > 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? I intend to provide some rfc patches later this week, for next release. -- David Marchand