From: Stephen Hemminger <stephen@networkplumber.org>
To: Alan Arondel <Alan.Arondel@enea.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Tx burst and ordered packets
Date: Thu, 10 Jun 2021 09:29:14 -0700 [thread overview]
Message-ID: <CAOaVG16aqZEQkyr8sfKQ_Qs-h-VeHUPEHz_v-pXEGqRx9XScYg@mail.gmail.com> (raw)
In-Reply-To: <PA4PR03MB71677F7EB1CC0FD430C6C0F9E9389@PA4PR03MB7167.eurprd03.prod.outlook.com>
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)
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.
>
> 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.
>
> Thank you for any reply.
>
> Regards,
> Alan.
>
> 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.
>
next prev parent reply other threads:[~2021-06-10 16:29 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 [this message]
2021-06-11 9:57 ` Van Haaren, Harry
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:
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=CAOaVG16aqZEQkyr8sfKQ_Qs-h-VeHUPEHz_v-pXEGqRx9XScYg@mail.gmail.com \
--to=stephen@networkplumber.org \
--cc=Alan.Arondel@enea.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).