DPDK usage discussions
 help / color / mirror / Atom feed
From: Jim Thompson <jim@netgate.com>
To: Alireza Sanaee <sarsanaee@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Capturing Pause Frames in DPDK Applications
Date: Tue, 21 Apr 2020 23:22:19 -0500	[thread overview]
Message-ID: <23CFFBA0-8F12-4017-9933-500D847029D1@netgate.com> (raw)
In-Reply-To: <7103100c-ff28-2ff8-deef-37b9a1877ae6@gmail.com>



> On Apr 21, 2020, at 10:50 PM, Alireza Sanaee <sarsanaee@gmail.com> wrote:
> 
> Dear all,
> 
> I'm wondering that if there is any chances to pass pause frames through a NIC and receive it in the DPDK application? Is there any ideas to practically make this modification?
> 
> I have read that Pause Frames are being consumed at ASIC level so it would not be possible to pass the frame to CPU. In that case, I'm just thinking of creating an artificial pause frame on arrival of a real Ethernet pause frame and push the artificial one to software, it might be crazy though but still capturing arrival event of an Ethernet pause frame remains a challenge.
> 
> In a DPDK less scenario, I'm thinking if a packet sniffer like Wireshark can capture a pause frame, then it means NIC is sending pause frames to higher layers I believe. Likewise in the DPDK scenario I should be able to see the pause frames maybe in the PMD driver?
> 
> Thanks,
> Alireza

Alireza,

What you seek is documented.

https://doc.dpdk.org/dts/test_plans/link_flowctrl_test_plan.html <https://doc.dpdk.org/dts/test_plans/link_flowctrl_test_plan.html>

testpmd> set mac_ctrl_frame_fwd on


Not all PMDs support this setting, though igb and i40e do.

      reply	other threads:[~2020-04-22  4:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22  3:50 Alireza Sanaee
2020-04-22  4:22 ` Jim Thompson [this message]

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=23CFFBA0-8F12-4017-9933-500D847029D1@netgate.com \
    --to=jim@netgate.com \
    --cc=sarsanaee@gmail.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).