DPDK usage discussions
 help / color / mirror / Atom feed
From: Sander Ubink <sanderubink@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Sending packets in specific order
Date: Mon, 23 Apr 2018 14:25:44 +0200	[thread overview]
Message-ID: <CADXUNsxFcODGuNmRYh67wLQOsdW4994rJH4KF4xyXQyfamrGtg@mail.gmail.com> (raw)

Hi,

I'm currently attempting to send a specific pattern of packets using
pktgen. When I dump the mbuf's that are being passed to rte_eth_tx_burst()
I can confirm that they are in the correct order. However, on the receiving
side, tcpdump shows a completely different order. The machines are directly
connected to each other using a QSFP cable. Is the reordering of packets
inherent to the implementation of DPDK or is there some way I can enforce
packets are being send in the order they are provided?

Kind regards,
Sander

             reply	other threads:[~2018-04-23 12:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 12:25 Sander Ubink [this message]
2018-04-23 12:42 ` Paul Emmerich

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=CADXUNsxFcODGuNmRYh67wLQOsdW4994rJH4KF4xyXQyfamrGtg@mail.gmail.com \
    --to=sanderubink@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).