[dpdk-dev] Error: unbind failed
Hello, I installed dpdk on ubuntu VM. when I tried to bind the device to the driver I received the following error: /dpdk-devbind.py --bind=uio_pci_generic eth3 Error: bind failed for :02:02.0 - Cannot bind to driver uio_pci_generic Error: unbind failed for :02:02.0 - Cannot open /sys/bus/pci/drivers//unbind I?m not looking for best performance on VM. Any ideas why I received this error ? Thanks.
[dpdk-dev] DPDK with VMXNET3
2016-08-21 12:01, Keren Hochman: > Hi, Hi, > I saw you removed from the git VMXNET3 user map. does this driver does not > support anymore in dpdk? thanks It is not removed, just unmaintained and moved here: http://dpdk.org/browse/old/vmxnet3-usermap/ Are you volunteer to maintain it? There is another (replacement) implementation using UIO/VFIO in http://dpdk.org/browse/dpdk/tree/drivers/net/vmxnet3
[dpdk-dev] DPDK with VMXNET3
Hi, I saw you removed from the git VMXNET3 user map. does this driver does not support anymore in dpdk? thanks
[dpdk-dev] Unable to start DPDK+Netshard
Hi , When I start netshard with dpdk-pmd stack , getting the below error RING: Cannot reserve memory Failed to create mempool for Tx RING: Cannot reserve memory Failed to create mempool for Tx Creating Rx mbuf pool 'dpdk_net_pktmbuf_pool8_rx' [1024 mbufs] ... RING: Cannot reserve memory Failed to create mempool for Tx Configured huge pages and binded NIC to DPDK drivers Please let me know how to resolve this issue, PFA nic binding / huge pages details. Thanks Jay The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com -- next part -- An embedded and charset-unspecified text was scrubbed... Name: loadtest_issue.txt URL: <http://dpdk.org/ml/archives/dev/attachments/20160821/a2186c86/attachment.txt>
[dpdk-dev] [PATCH] net/i40e: fix parsing QinQ packets type issue
> -Original Message-
> From: Xing, Beilei
> Sent: Friday, August 19, 2016 11:20 AM
> To: Wu, Jingjing
> Cc: dev at dpdk.org; Xing, Beilei
> Subject: [PATCH] net/i40e: fix parsing QinQ packets type issue
>
> Previously, PTYPE filed in the RX descriptors is not set properly
> for QinQ packets, wrong PTYPE is generated because outer Tag did
> not have ORT/PIT configured.
> Fix this issue by configuring ORT/PIT.
>
> Fixes: 4861cde46116 ("i40e: new poll mode driver")
>
> Signed-off-by: Beilei Xing
> ---
> drivers/net/i40e/i40e_ethdev.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/net/i40e/i40e_ethdev.c b/drivers/net/i40e/i40e_ethdev.c
> index 55c4887..ba0eca0 100644
> --- a/drivers/net/i40e/i40e_ethdev.c
> +++ b/drivers/net/i40e/i40e_ethdev.c
> @@ -747,8 +747,10 @@ static inline void i40e_flex_payload_reg_init(struct
> i40e_hw *hw)
> I40E_WRITE_REG(hw, I40E_GLQF_ORT(20), 0x0031);
> I40E_WRITE_REG(hw, I40E_GLQF_ORT(23), 0x0031);
> I40E_WRITE_REG(hw, I40E_GLQF_ORT(63), 0x002D);
> + I40E_WRITE_REG(hw, I40E_GLQF_ORT(40), 0x0029);
Setting of GLQF_ORT(40) and GLQF_PIT(16) is for outer vlan, but not for
Flexible payload.
So it may not be suitable to put the code in i40e_flex_payload_reg_init.
How about change the function's name and add comments in code?
> /* GLQF_PIT Registers */
> + I40E_WRITE_REG(hw, I40E_GLQF_PIT(9), 0x9420);
> I40E_WRITE_REG(hw, I40E_GLQF_PIT(16), 0x7480);
> I40E_WRITE_REG(hw, I40E_GLQF_PIT(17), 0x7440);
> }
> --
> 2.5.0
[dpdk-dev] SR-IOV: dpdk16.07 on guest and ixgbe 3.19.1 on host - will that be a problem ? (requested invalid api version)
HI Gopakumar, > -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Gopakumar > Choorakkot Edakkunni > Sent: Saturday, August 20, 2016 10:57 PM > To: dev at dpdk.org > Subject: [dpdk-dev] SR-IOV: dpdk16.07 on guest and ixgbe 3.19.1 on host - will > that be a problem ? (requested invalid api version) > > I see the below message "requested invalid api version" on host ? Will that > be an > issue or is it benign ? Should I upgrade the host ixgbe to a later version ? > > On the host: > > *[69576.199458] ixgbe :88:00.1 p4p2: VF 2 requested invalid api version > 3* It means ixgbe doesn't support ixgbe_mbox_api_12. I suggest using something newer.
