From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lilijun Subject: Re: Possibility to unbind interface by DPDK Date: Thu, 16 Oct 2014 20:12:56 +0800 Message-ID: <543FB648.5010200@huawei.com> References: <7C4248CAE043B144B1CD242D275626532FDDE618@IRSMSX104.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit To: Return-path: In-Reply-To: <7C4248CAE043B144B1CD242D275626532FDDE618-kPTMFJFq+rGvNW/NfzhIbrfspsVTdybXVpNB7YpNyf8@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On 2014/10/16 19:45, Walukiewicz, Miroslaw wrote: > I have a question regarding unbinding Linux interface from EAL. > > This feature was present up to dpdk 1.4 and next it was removed. > > It was available under RTE_EAL_UNBIND_PORTS flag. > > Is there a possibility to get this feature back in the next releases? > > Unbinding interfaces from EAL makes possible reading network interface parameters like IP address, MTU, VLAN configuration from dpdk applications. > > When Linux interface is unbound before application start this information is lost for application. The same problem was found. Might an alternative be to actually bind the NICs to DPDK uio driver like the dpdk_nic_bind.py scipts after getting that NIC parameters in your application . > > Mirek > >