DPDK usage discussions
 help / color / mirror / Atom feed
From: Paul Rafferty <paul.rafferty@calnexsol.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Sending MAC control frames to host application using the i40e pmd.
Date: Mon, 3 Apr 2023 11:02:48 +0000	[thread overview]
Message-ID: <LO0P265MB6551FB2BD204657DA198B5AFF7929@LO0P265MB6551.GBRP265.PROD.OUTLOOK.COM> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1681 bytes --]

Hello,

I have an application that processes packets received by an Intel XXV710 NIC via the i40e PMD in DPDK. I need all MAC control frame packets to be passed to the application as regular packets, but I have been unable to configure the device to do this successfully, all control frames seem to be consumed by the hardware and do reach the application queues at all. Referencing the datasheet for this card and the i40e PMD, I need to enable MAC control frame forwarding.

I have tried to configure the card using the rte_eth_dev_flow_ctrl_set call with the following settings in the struct rte_eth_fc_conf:
      .mode = RTE_FC_NONE;
      .high_water = 0;
      .low_water = 0;
      .pause_time = 0;
      .send_xon = 0;
      .mac_ctrl_frame_fwd = 1;
      .autoneg = 0;

The call returns successfully yet checking with rte_eth_dev_flow_ctrl_get shows that the value for .mac_ctrl_frame_fwd is still zero and I cannot see control frames in my application. How can I configure this card to pass these frames?

Thanks,

Paul.
Paul Rafferty R&D Departmentt: +44 1506 671416e: paul.rafferty@calnexsol.comw: calnexsol.comNew Product

The SNE-X is a total solution to the problem of real-world Ethernet testing. It combines comprehensive and efficient network emulation for 5G, Data Center, and Cloud applications. Click for more information.

Calnex Solutions
Oracle Campus
Linlithgow
EH49 7LR
United KingdomCalnex Solutions plc is registered in Scotland. Registration number: SC299625. Registered office: Oracle Campus, Linlithgow, Scotland, EH49 7LR, United Kingdom.

[-- Attachment #1.2: Type: text/html, Size: 8813 bytes --]

[-- Attachment #2: Type: image/gif, Size: 4103 bytes --]

[-- Attachment #3: Type: image/gif, Size: 1691 bytes --]

[-- Attachment #4: Type: image/gif, Size: 1614 bytes --]

[-- Attachment #5: Type: image/gif, Size: 1644 bytes --]

[-- Attachment #6: Type: image/gif, Size: 1698 bytes --]

[-- Attachment #7: Type: image/jpeg, Size: 7270 bytes --]

                 reply	other threads:[~2023-04-03 11:02 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=LO0P265MB6551FB2BD204657DA198B5AFF7929@LO0P265MB6551.GBRP265.PROD.OUTLOOK.COM \
    --to=paul.rafferty@calnexsol.com \
    --cc=users@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).