From: sachin gupta <sachingg@yahoo.com>
To: "users@dpdk.org" <users@dpdk.org>,
"Nutman, Richard" <Richard.Nutman@grassvalley.com>
Subject: Re: [dpdk-users] Sequential UDP packets
Date: Wed, 13 Nov 2019 15:46:28 +0000 (UTC) [thread overview]
Message-ID: <1289692801.260299.1573659988061@mail.yahoo.com> (raw)
In-Reply-To: <9b57baa273c94968b859577e5a384245@DCRIC1EXC05PA.mcp.local>
Hi Sarvesh, Richard
In general any router is not supposed to re-order the packets, even when the packets are received from outside.In this case, the packets are created internally only. So as such UDP protocol makes no difference.
One reason i can think is the use of multiple queues, or threads for transmission.
Sachin
On Wednesday, November 13, 2019, 03:24:35 PM GMT+5:30, Nutman, Richard <richard.nutman@grassvalley.com> wrote:
Hi Sarvesh,
UDP is not a reliable protocol, not even for the order of packets you receive.
You have to re-order them when you receive them. For example using a sequence number to index them into a circular buffer.
Wireshark does not re-order UDP packets but merely shows them in the order they were captured.
Regards,
Richard
> -----Original Message-----
> From: Sarvesh Verma [mailto:sarveshfwecverma79@gmail.com]
> Sent: 13 November 2019 07:56
> To: users@dpdk.org
> Subject: [dpdk-users] Sequential UDP packets
>
> Hey DPDK users,
>
> Since last two months I'm struggling to generate my own sequential UDP
> packets through DPDK. At receiving side my packets counts are matching but
> are not in sequence in Wireshark.
> Expected- 1,2,3,4,5,6,7,8,9,10.........
> Getting-1,4,6,8,9,2,3,5,7,10........…
>
> Hope anyone will reply soon.
>
> Thank you
> Sarvesh Verma
**********************************************************************
DISCLAIMER:
Privileged and/or Confidential information may be contained in this message. If you are not the addressee of this message, you may not copy, use or deliver this message to anyone. In such event, you should destroy the message and kindly notify the sender by reply e-mail. It is understood that opinions or conclusions that do not relate to the official business of the company are neither given nor endorsed by the company. Thank You.
next prev parent reply other threads:[~2019-11-13 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 7:56 Sarvesh Verma
2019-11-13 9:54 ` Nutman, Richard
2019-11-13 15:46 ` sachin gupta [this message]
2019-11-13 15:52 ` Pathak, Pravin
2019-11-14 14:27 ` Tom Barbette
2019-11-15 0:23 ` Pierre Laurent
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=1289692801.260299.1573659988061@mail.yahoo.com \
--to=sachingg@yahoo.com \
--cc=Richard.Nutman@grassvalley.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).