From: Stephen Hemminger <stephen@networkplumber.org>
To: Igor Gutorov <igootorov@gmail.com>
Cc: users@dpdk.org
Subject: Re: net_ring, net_memif are missing RX-missed counter
Date: Wed, 15 Mar 2023 11:44:36 -0700 [thread overview]
Message-ID: <20230315114436.0af987cd@hermes.local> (raw)
In-Reply-To: <CAL7bPf2Nmo9rvVHAOoz9NdJnp2tR+TYcJAXwmiaqTDvY+s-R-w@mail.gmail.com>
On Wed, 15 Mar 2023 20:41:06 +0300
Igor Gutorov <igootorov@gmail.com> wrote:
> Hi,
>
> I've noticed that net_ring and net_memif PMDs always report RX-missed
> counter as 0. Is it just a feature that is missing, or is it something that
> fundamentally cannot be implemented for these PMDs?
Rx missed is used by hardware devices to indicate the packets that
driver could not receive because of lack of resources. It has to come
from the hardware (or maybe the host in a virtual driver).
There probably is not an analogous counter in memif because it would
have to be maintained by the other side (sender) and then have a control
API for it. If it is your application, then the sending side could
report how many times tx_burst was unable to send packets.
prev parent reply other threads:[~2023-03-15 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 17:41 Igor Gutorov
2023-03-15 18:44 ` 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=20230315114436.0af987cd@hermes.local \
--to=stephen@networkplumber.org \
--cc=igootorov@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).