DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Alan Arondel <arondel.alan@gmail.com>
Cc: users@dpdk.org
Subject: Re: rte_eth_tx_burst return 0 after some time
Date: Mon, 9 Sep 2024 09:39:53 -0700	[thread overview]
Message-ID: <20240909093953.433da8ef@hermes.local> (raw)
In-Reply-To: <CAGhLx=k7-BWDrwpyLykpxDTAHdgDw3-AuRrpC36tbkvJCLaXtA@mail.gmail.com>

On Mon, 9 Sep 2024 15:25:23 +0200
Alan Arondel <arondel.alan@gmail.com> wrote:

> Hello Everyone,
> 
> I'm trying to add an export module to my application. I use DPDK
> version 20.11, a 82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb
> and the vfio-pci driver.
> port configuration is the following:
> 
> port_conf->txmode.mq_mode = ETH_MQ_TX_NONE;
> port_conf->txmode.offloads = DEV_TX_OFFLOAD_MULTI_SEGS;
> 
> I use only 1 queue on the card and the configuration is the following :
>     nb_desc : 4096
>     rs_threshold : 32
>     free_threshold : 32
> 
> I have an issue where at some point during the lifetime of the
> application, the rte_eth_tx_burst return only 0 and nothing can be
> done once it is stuck after several seconds of the beginning of
> transmission.

Looks like the driver you are passing packets is unable to send
packets. Most drivers have an internal transmit ring, so either
the hardware is not consuming the packets from the ring or the
packets have been sent but the transmit ring cleanup logic has
not been called.

In most cases, problems are in your application. Best to start
with making sure simple applications like testpmd and l3fwd
work with similar configurations.

      reply	other threads:[~2024-09-09 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-09 13:25 Alan Arondel
2024-09-09 16:39 ` Stephen Hemminger [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=20240909093953.433da8ef@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=arondel.alan@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).