DPDK patches and discussions
 help / color / mirror / Atom feed
From: Mohan Gyara <sreemohangyara@yahoo.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: ixgbevf in dpdk doesn't seems to work (dpdk-stable-19.11.5)
Date: Fri, 3 Jun 2022 08:14:00 +0000 (UTC)	[thread overview]
Message-ID: <1455096021.5344065.1654244040257@mail.yahoo.com> (raw)
In-Reply-To: <1455096021.5344065.1654244040257.ref@mail.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]

Hi Team,
In our application we use 2 interfaces one to communicate towards gNB and another to communicate with higher layers in a UE simulator NR stack. Now we use a PCI whose driver is i40e and is bind to dpdk vfio-pci driver and this works perfectly towards higher layer, but the other interface PCI whose is ixgbe driver is bind to vfio-pci dpdk driver and has some issues. 
The issues are:1. Application crashes when "rte_eth_dev_mac_addr_add" function is called when return with -1.  "on a 82599 VF, adding again the same MAC addr is not an idempotent operation..." this is a comment, but the function ixgbevf_add_mac_addr  return -1 when memcmp(hw->mac.perm_addr, mac_addr) == 0) is true. But above I commented the "return -1" and just returned from it, so crash is not seen.2. After above 1, application is started successfully but then I do not see any messages coming on this interface. This is the problem? 
Could you guide me what is the issue? I see only issue with ixgbvf but not for i40evf.
I am using dpdk-stable-19.11.5 version.

Kindly help me here.
Regards,Mohan

[-- Attachment #2: Type: text/html, Size: 3583 bytes --]

       reply	other threads:[~2022-06-03  8:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1455096021.5344065.1654244040257.ref@mail.yahoo.com>
2022-06-03  8:14 ` Mohan Gyara [this message]
2022-06-03  8:59   ` Bruce Richardson
2022-06-04 13:50     ` Mohan Gyara
     [not found] <543678175.5148402.1654204621609.ref@mail.yahoo.com>
2022-06-02 21:17 ` Mohan Gyara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1455096021.5344065.1654244040257@mail.yahoo.com \
    --to=sreemohangyara@yahoo.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).