DPDK usage discussions
 help / color / mirror / Atom feed
From: Pierre Laurent <pierre.laurent@emutex.com>
To: Sarvesh Verma <sarveshfwecverma79@gmail.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Sequential UDP packets
Date: Fri, 15 Nov 2019 00:23:35 +0000	[thread overview]
Message-ID: <AM0P190MB06254D9E8C90047DA340560AE3700@AM0P190MB0625.EURP190.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAA7bc+Ym8yTWX2WAG266-Y-maO1zTod7m-3+xCda-XEPrU=V=Q@mail.gmail.com>

HI

Without much information , it is very hard to imagine what you are doing and what you are getting.

From the packet numbers you provide, it looks like you are seeing all packets, and it is not a packet loss problem.

DPDK itself does not reorder the packets.
But your DPDK setup might be built from multiple path and transmit packets from multiple threads and /or multiple queues , or both, or over multiple interfaces.


If you are sure to use one single TX thread, one single TX queue, one single TX interface to transmit your packets with DPDK, then this cannot be a DPDK problem.

The problem can be on the receive side where you are using wireshark with some standard OS and standard driver. It is very frequent in standard OS and standard drivers to implement multiple RX queues (e.g. Windows, Ubuntu ...).  With such a config, packets with the same tuple5 (source IP, dest IP, source Port, dest Port, protocol  https://www.techopedia.com/definition/28190/5-tuple ) are not reordered and assigned to the same RX queue.

If you number your packets by changing one of the elements of the tuple 5, e.g. the destination udp  port, then RX packets will be sent to different RX queues, this standard   feature is known as receive-side-scaling (RSS)   https://docs.microsoft.com/en-us/windows-hardware/drivers/network/introduction-to-receive-side-scaling  . Then Wireshark would get the packets in any order, depending on polling strategies and priorities, rates and packet distributions in the different queues. There are options in most OS to set the number of queues, or disable RSS.

Alternatively, make sure your packets have all the same "tuple5", and if you want to put some sequential number, I suggest you do it in the UDP payload.

This response is a guess, because you provided NO information about your environment, your setup, any packet size, any packet rate, any packet dump nor investigations you already did.

Regards,

Pierre



________________________________
From: users <users-bounces@dpdk.org> on behalf of Sarvesh Verma <sarveshfwecverma79@gmail.com>
Sent: Wednesday 13 November 2019 07:56
To: users@dpdk.org <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

      parent reply	other threads:[~2019-11-19  9:03 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
2019-11-13 15:52     ` Pathak, Pravin
2019-11-14 14:27       ` Tom Barbette
2019-11-15  0:23 ` Pierre Laurent [this message]

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=AM0P190MB06254D9E8C90047DA340560AE3700@AM0P190MB0625.EURP190.PROD.OUTLOOK.COM \
    --to=pierre.laurent@emutex.com \
    --cc=sarveshfwecverma79@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).