DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shaham Fridenberg <ShahamF@Radware.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] sriov on fm10k card
Date: Mon, 28 Nov 2016 11:01:31 +0000	[thread overview]
Message-ID: <2E654B490240B7449C846A96A8D8FE0C0116607732@ILMB1.corp.radware.com> (raw)

Hi all,

I have an fm10k card with dual 100G ports, I am running a DPDK application that binds 2 virtual functions to it. I have trouble receiving traffic in my vnfs on fm10k VFs.

Current analysis:



1.       From rdif debugging I see that it doesn't add the port of the VF in the switching table.

2.       Running l2fwd in the same vm 1. Doesn't occur. (the port info and mac is added properly to the switch manager and the traffic works.)

3.       Port initialization code in my application and in l2fwd have been compared and equalized.



4.       The entry for the port is added in the rdif when we call the function fm10k_update_uc_addr(hw, hw->mac.dglort_map, data->mac_addrs[mac_index].addr_bytes,vlan_id, on, 0);

In my application this function is called too, but I noticed that the values of hw->mac.dglort_map are different.

In l2fwd it's updated with FM10K_DGLORTMAP_ZERO, in function that handles a msg from PF: fm10k_msg_lport_state_vf (according to documentation, this handler is meant to capture the indication from the PF that we are ready to bring up the interface).

In the case of my app this handler is never called. For some reason the PF does not send this message and I suspect this could be the reason why the VF mac entry is not learned in the Switch.



Any hint/ ideas of what I could be missing?



Thanks

                 reply	other threads:[~2016-11-28 11:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2E654B490240B7449C846A96A8D8FE0C0116607732@ILMB1.corp.radware.com \
    --to=shahamf@radware.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).