From: Antonio Di Bacco <a.dibacco.ks@gmail.com>
To: users@dpdk.org
Subject: xxx_DESCS_PER_LOOP workaround
Date: Thu, 7 Jul 2022 18:01:17 +0200 [thread overview]
Message-ID: <CAO8pfFmU8sLYwEBQA1CS8+NMtNZ8dEbEGuyZ2i=C+3vU7+0tMQ@mail.gmail.com> (raw)
I'm using the ice PMD driver and, luckily, before going mad, I
discovered that an rte_eth_rx_burst with a burst size of 1 will never
succeed even if packets have arrived on the network card. This is due
to the fact that ICE_DESCS_PER_LOOP is set to 4 or 8 and then you need
to use a burst size not lower than 4 or 8.
Now, I have an application where a single packet (9000 bytes) has to
be delivered through the network with the lowest possible latency.
Is it possible to workaround this limitation by accepting the
performance degradation?
I read that there is a "runtime" option -a <BDF>,rx_low_latency=1
but I'm not sure if this will be a workaround.
reply other threads:[~2022-07-07 16:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAO8pfFmU8sLYwEBQA1CS8+NMtNZ8dEbEGuyZ2i=C+3vU7+0tMQ@mail.gmail.com' \
--to=a.dibacco.ks@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).