Hi Anatoly, I might have used the term 'initialization' in a wrong fashion. But I have confirmed, the issue was related to this commit (which Thomas brought to my notice) --
http://dpdk.org/browse/dpdk/commit/?id=18f02ff75949de9c2468 The above should get you the context for the original issue. Regards -Prashant -----Original Message----- From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Burakov, Anatoly Sent: Friday, April 11, 2014 2:29 PM To: dev at dpdk.org Subject: Re: [dpdk-dev] IGB_UIO port unbinding Hi Prashant, > 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. > Did you try it on the latest 1.6.x code (that option was removed)? More to the point, I can't see how this would be relevant to vmxnet3 initialization. All this config option does is automatically unbinds NICs for you, which is something you can do manually with the included igb_uio_bind.py/pci_unbind.py script anyway. Could you please elaborate on how exactly this option helped with vmxnet3 initialization? Best regards, Anatoly Burakov DPDK SW Engineer -------------------------------------------------------------- Intel Shannon Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 Business address: Dromore House, East Park, Shannon, Co. Clare "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 privileged 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 message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
