From: Sungho Hong <maverickjin88@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] The purpose of Reorder Library and IP fragmentation in DPDK
Date: Sat, 15 Sep 2018 16:55:20 -0700 [thread overview]
Message-ID: <CAK8vx=jSqCZhf3X+Os0xim3cn_gzX_jw4Xmp=QNcsyVaScpHFQ@mail.gmail.com> (raw)
Hello, DPDK users,
I am trying to send 4096 byte of message by splitting the message into 4
packets.
However, Simply sending the messages in bursts does not guarantee that the
messages will be received in order.
For example if I send 3 messages in 3 bursts
I receive messages like this below
ex) send (3 burst)
[1111111] [22222] [33333]
ex) recv
[33333] [22222] [1111111]
So In order to solve this issue, I was struggling with reorder library and
ip fragmentation in l3fwd example.
Which library do I have to use in order to achieve the result like this
below? (IP fragmentation or Reorder Library)
ex) send (3 burst)
[1111111] [22222] [33333]
ex) recv
[1111111] [22222] [33333]
reply other threads:[~2018-09-15 23:55 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='CAK8vx=jSqCZhf3X+Os0xim3cn_gzX_jw4Xmp=QNcsyVaScpHFQ@mail.gmail.com' \
--to=maverickjin88@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).