From: Sungho Hong <shong59@asu.edu>
To: users@dpdk.org
Subject: [dpdk-users] Preventing DPDK packet loss in L2 forwarding
Date: Thu, 14 Dec 2017 12:13:47 -0700 [thread overview]
Message-ID: <CAKf1RwA1cdv2xMNgJpL7DCRKnO6u_CsXFPeWqSUfBqfyGa1j9g@mail.gmail.com> (raw)
Hello I have implemented pingpong for DPDK. with the client sending the
packets and the server receiving the packets and then returning them.
The server part is implemented similar to the L2 forwarding sample in the
DPDK official website.
While doing the L2 forwarding I have noticed that there are packet losses
while I forward the the packets from the receiver queue to the transfer
queue.
My question is ... is there a way to make the packet loss into zero?
I could not find the solution to this since the sample applications from
DPDK website all have packet losses.
the packet losses are counted by the callback function below
rte_eth_tx_buffer_set_err_callback(tx_buffer[portid],
rte_eth_tx_buffer_count_callback, &port_statistics[portid].dropped);
this is the result I have from the L2 forwarding
Port statistics ====================================
Statistics for port 0 ------------------------------
Packets sent: 384126
Packets received: 379889
Packets dropped: 4237
Aggregate statistics ===============================
Total packets sent: 384126
Total packets received: 379889
Total packets dropped: 4237
====================================================
since my implementation is just pingpong and have very simple
implementation, I don't believe that there should be any packet losses in
my case.
Thank you for reading this letter
Sungho Hong
reply other threads:[~2017-12-14 19:14 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=CAKf1RwA1cdv2xMNgJpL7DCRKnO6u_CsXFPeWqSUfBqfyGa1j9g@mail.gmail.com \
--to=shong59@asu.edu \
--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).