DPDK usage discussions
 help / color / mirror / Atom feed
From: "Gábor LENCSE" <lencse@hit.bme.hu>
To: users@dpdk.org
Subject: Re: rte_eth_tx_burst() always returns 0 in tight loop
Date: Sun, 3 Jul 2022 22:18:46 +0200	[thread overview]
Message-ID: <2ca6fffa-05df-9882-34e9-6c13dc2cc28f@hit.bme.hu> (raw)
In-Reply-To: <CAO8pfFnMXA71rweMs6j4eK3w0trkWqxHfe9Ek1kDT55v7r1MKQ@mail.gmail.com>

Dear Antonio,

According to my experience, the rte_eth_tx_burst() function reports the 
packets as "sent" (by a non-zero return value), when they are still in 
the transmit buffer.

(If you are interested in the details, you can see them in Section 3.6.5 
of this paper: http://www.hit.bme.hu/~lencse/publications/e104-b_2_128.pdf )

Therefore, I think that the return value of 0 may mean that 
rte_eth_tx_burst() can't even commit itself for the future delivery of 
the packets. I could only guess why. E.g. all its resources have been 
exhausted.

Best regards,

Gábor


7/3/2022 5:57 PM keltezéssel, Antonio Di Bacco írta:
> I'm trying to send packets continuously in a  tight loop with a burst
> size of 8 and packets are 9600 bytes long.
> If I don't insert a delay after the rte_eth_tx_burst it always returns 0.
>
> What's the explanation of this behaviour ?
>
> Best regards,
> Antonio.


  reply	other threads:[~2022-07-03 20:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-03 15:57 Antonio Di Bacco
2022-07-03 20:18 ` Gábor LENCSE [this message]
2022-07-06  7:21   ` Antonio Di Bacco
2022-07-06 15:00     ` Stephen Hemminger
2022-07-07 14:30       ` Antonio Di Bacco
2022-09-26 15:36         ` Antonio Di Bacco
2022-09-26 17:24           ` Stephen Hemminger
2022-07-06 15:03     ` Gábor LENCSE

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=2ca6fffa-05df-9882-34e9-6c13dc2cc28f@hit.bme.hu \
    --to=lencse@hit.bme.hu \
    --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).