From: Alireza Sanaee <sarsanaee@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Capturing Pause Frames in DPDK Applications
Date: Wed, 22 Apr 2020 11:50:04 +0800 [thread overview]
Message-ID: <7103100c-ff28-2ff8-deef-37b9a1877ae6@gmail.com> (raw)
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
next reply other threads:[~2020-04-22 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 3:50 Alireza Sanaee [this message]
2020-04-22 4:22 ` Jim Thompson
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=7103100c-ff28-2ff8-deef-37b9a1877ae6@gmail.com \
--to=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).