DPDK usage discussions
 help / color / mirror / Atom feed
From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	Alan Arondel <Alan.Arondel@enea.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Tx burst and ordered packets
Date: Fri, 11 Jun 2021 09:57:13 +0000
Message-ID: <BYAPR11MB3143E5EE932126395CF77409D7349@BYAPR11MB3143.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAOaVG16aqZEQkyr8sfKQ_Qs-h-VeHUPEHz_v-pXEGqRx9XScYg@mail.gmail.com>

> -----Original Message-----
> From: users <users-bounces@dpdk.org> On Behalf Of Stephen Hemminger
> Sent: Thursday, June 10, 2021 5:29 PM
> To: Alan Arondel <Alan.Arondel@enea.com>
> Cc: users@dpdk.org
> Subject: Re: [dpdk-users] Tx burst and ordered packets
> Are you using RSS on the receiver.
> Packets sent in one burst should go out in order (if not it is a Intel
> driver bug)

[Sidenote: its best practice to reply inline when answering questions on mailing lists.]

> On Mon, Jun 7, 2021 at 3:09 PM Alan Arondel <Alan.Arondel@enea.com> wrote:
> > Hello everyone,
> >
> > I just wanted to know if a burst of packets using rte_eth_tx_burst are
> > send in the same order of the parameter struct rte_mbuf ** tx_pkts ?
> > I tried the skeleton sample which use this api and can confirm that the
> > received packets are not in the right order. Probably I'm doing something
> > wrong somewhere.

Stephen is correct in that the rte_mbuf **tx_pkts order is the order packets
should be sent on the wire. Indeed if they are not, it is a driver bug, and should
be fixed.

Before we jump to that conclusion, can I suggest we look at how packet ordering
is being measured? Keep in mind packets could be dropped along the way, so
if we count (N) and (N+1) on the next packet, and then validate ordering by ensuring
the received packets are exactly (N, N+1), then a drop would suggest re-ordering issues...

> > I use the driver net_i40e.
> > Dpdk version 20.11.1
> > Compilation withtout any specifique parameters (meson
> > configure/ninja/ninja install)
> > I cannot find any discussion or information about this.

I expect that would work correctly.

> > Thank you for any reply.
> >
> > Regards,
> > Alan.

Regards, -Harry

PS: Please try to avoid sending the below to public mailing lists like DPDK:

> > This message, including attachments, is CONFIDENTIAL. It may also be
> > privileged or otherwise protected by law. If you received this email by
> > mistake please let us know by reply and then delete it from your system;
> > you should not copy it or disclose its contents to anyone. All messages
> > sent to and from Enea may be monitored to ensure compliance with internal
> > policies and to protect our business. Emails are not secure and cannot be
> > guaranteed to be error free as they can be intercepted, amended, lost or
> > destroyed, or contain viruses. The sender therefore does not accept
> > liability for any errors or omissions in the contents of this message,
> > which arise as a result of email transmission. Anyone who communicates with
> > us by email accepts these risks.
> >

  reply	other threads:[~2021-06-11  9:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 22:09 Alan Arondel
2021-06-10  9:37 ` Alan Arondel
2021-06-10 16:29 ` Stephen Hemminger
2021-06-11  9:57   ` Van Haaren, Harry [this message]
2021-06-13 12:53 Alan Arondel

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BYAPR11MB3143E5EE932126395CF77409D7349@BYAPR11MB3143.namprd11.prod.outlook.com \
    --to=harry.van.haaren@intel.com \
    --cc=Alan.Arondel@enea.com \
    --cc=stephen@networkplumber.org \
    --cc=users@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git