From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11]) by dpdk.org (Postfix) with ESMTP id 1F7F2690F for ; Thu, 10 Apr 2014 18:02:57 +0200 (CEST) Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id C55D836B36; Thu, 10 Apr 2014 21:34:12 +0530 (IST) Received: from GUREXHT01.ASIAN.AD.ARICENT.COM (gurexht01.asian.ad.aricent.com [10.203.171.136]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by jaguar.aricent.com (Postfix) with ESMTP id B8FA136B35; Thu, 10 Apr 2014 21:34:12 +0530 (IST) Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.134]) by GUREXHT01.ASIAN.AD.ARICENT.COM ([10.203.171.136]) with mapi; Thu, 10 Apr 2014 21:34:13 +0530 From: Prashant Upadhyaya To: Thomas Monjalon , "Burakov, Anatoly" Date: Thu, 10 Apr 2014 21:34:04 +0530 Thread-Topic: [dpdk-dev] IGB_UIO port unbinding Thread-Index: Ac9UsY9e9YOzwB+cS5yLsgRw9tU7igAJKqNw Message-ID: References: <2817508.QMqjK3mPRB@xps13> In-Reply-To: <2817508.QMqjK3mPRB@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-TM-AS-MML: No Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] IGB_UIO port unbinding X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2014 16:02:58 -0000 Hi, There was a usecase with ESXi VMXNET3 NIC where I had to use this parameter= set to Y to make it work. So kindly ensure that the initialization of vmxnet3 NIC is not vulnerable. Regards -Prashant -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon Sent: Thursday, April 10, 2014 5:10 PM To: Burakov, Anatoly Cc: dev@dpdk.org Subject: Re: [dpdk-dev] IGB_UIO port unbinding Hi, 2014-04-10 09:39, Burakov, Anatoly: > As you may or may not know, the CONFIG_RTE_EAL_UNBIND_PORTS was > deprecated in the official Intel(r) DPDK 1.6.0 release package. > However, the code itself (e.g. in lib/librte_eal/linuxapp/eal_pci.c > and other places) to support that config option was not removed. My > question would be, would anyone be opposed to a patch to remove that > code entirely? E.g. does anyone use that functionality? On my side, it's OK to remove it. I think you can prepare the patch and we'll wait 1 week before applying it. If nobody complains, this feature will be definitely removed. -- Thomas "DISCLAIMER: This message is proprietary to Aricent and is intended solely = for the use of the individual to whom it is addressed. It may contain privi= leged or confidential information and should not be circulated or used for = any purpose other than for what it is intended. If you have received this m= essage in error, please notify the originator immediately. If you are not t= he intended recipient, you are notified that you are strictly prohibited fr= om using, copying, altering, or disclosing the contents of this message. Ar= icent accepts no responsibility for loss or damage arising from the use of = the information transmitted by this email including damage from virus."