From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 0B3CBA0C43 for ; Thu, 10 Jun 2021 18:29:32 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 886794067C; Thu, 10 Jun 2021 18:29:31 +0200 (CEST) Received: from mail-lj1-f178.google.com (mail-lj1-f178.google.com [209.85.208.178]) by mails.dpdk.org (Postfix) with ESMTP id 809254003C for ; Thu, 10 Jun 2021 18:29:29 +0200 (CEST) Received: by mail-lj1-f178.google.com with SMTP id x14so5743489ljp.7 for ; Thu, 10 Jun 2021 09:29:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EQgHxaI2yu6+iZnkdrmLKJkYBaAetepsmSrQG73EACg=; b=Nuuh+goUi5MzsU9UDGQ6VLLHYRfCifekuA4Ovt2gAbeRgNcGnUjf6pLLn/9ufqfzDc YFSVoS+SKgO6EWkyI+VD87bNxIuthZNLmF0LEfQNkrJc+nbylpcq9UZTzZm2gMY9o4+I gz51ONhH6U16RNu68JgQa2EoL1C+PSH1+BAk9WfjqZ9q36ZiEVb7ZRNUpXX3Cc1Lidng 834aZ86VMgazrFiNOPdf4uccGbKSoJOyCo9jXymOYlvhoaKNHYu/fSY08zGM+Z3AlaWz 2KLUyQgn1hpOlYS9Wffey7EJOlJb8w4Gg2zzUwcKrKZqG025CtsA/jJjtm98U1DSMSAd gu+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EQgHxaI2yu6+iZnkdrmLKJkYBaAetepsmSrQG73EACg=; b=OvINmIafR1BgGqE3UbSTsE1eephPfAkRrjFIixhuW3lfPxV691u0eKf3QJtmpvzJFD xv3PmHCnZOe4FV71F++pi9HEc8zCk84uUUysCYyErC87QsmPVUxNJdRwQSYFAAN52RZH DiCFqiPsSEhrUmA7D18Ut6jo2InDV6PAMCVsrA21alxO6KGQZhu1wwJE+uiGcToxJ7sd WIz0qNevvLiwDj9duIn784LgC+MWqTbGbSrgwVqheN05iKOOiuyofZIV/nonXXMqKSIi 9WpfLwTcrTDzBkfmKG4Y+XRjlGIlIO5ZNYytaOcdJUGH4rj+0SlOc7ehLxPlNhi3TmQP eB2w== X-Gm-Message-State: AOAM533pg0i58QsohpR8N6KCg19RJVPuFtBG5DSQaCSWaTe20+NHE2y/ 35N+++Vjhrt9ZgrdGZbeEv86qpkvZmCqmbi+mUA74QkAkMxybQ== X-Google-Smtp-Source: ABdhPJwCfz3uvm2PRYLeF7Mxg6uEtLz6nmjJG2wNM65N0mA2J4Sc8l9QAQG+g5nkmoKSWLhz4x+EnPKoMz3iM8YKL2U= X-Received: by 2002:a2e:9802:: with SMTP id a2mr2811126ljj.232.1623342567523; Thu, 10 Jun 2021 09:29:27 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Stephen Hemminger Date: Thu, 10 Jun 2021 09:29:14 -0700 Message-ID: To: Alan Arondel Cc: "users@dpdk.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [dpdk-users] Tx burst and ordered packets X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" 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 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. >