From: Stephen Hemminger <stephen@networkplumber.org>
To: Gaurav Bansal <zeebee48@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] packet drops with missing rxdIdx count in vmxnet3
Date: Mon, 30 Sep 2019 07:59:38 -0700 [thread overview]
Message-ID: <20190930075938.77a2c70d@hermes.lan> (raw)
In-Reply-To: <CAFQQEmDWQ5b31VP3t=WCxL-gLW2J7JM6JXXDiwDxwHB01m6yjg@mail.gmail.com>
On Mon, 30 Sep 2019 11:22:19 +0530
Gaurav Bansal <zeebee48@gmail.com> wrote:
> hi all,
> havn't heard back on this so far. Can anyone please let me know of the
> possible reasons for the NIC to skip some of the indexes of the descriptor
> ring in the Rx path (as also shown by the vmxnet3 logs in my previous mail)
> ?
> thanks,
> gaurav
>
A packet can span multiple segments if your receive mbuf is too small to fit
all the data. That would cause the receive data to create a chained mbuf.
next prev parent reply other threads:[~2019-09-30 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 10:39 [dpdk-users] packet drops seen once the no of rxd pkts reach the ring size Gaurav Bansal
2019-09-26 5:15 ` Gaurav Bansal
2019-09-26 5:16 ` Stephen Hemminger
2019-09-26 7:55 ` Gaurav Bansal
2019-09-28 8:47 ` [dpdk-users] packet drops with missing rxdIdx count in vmxnet3 Gaurav Bansal
2019-09-30 5:52 ` Gaurav Bansal
2019-09-30 14:59 ` Stephen Hemminger [this message]
2019-10-09 6:11 ` Gaurav Bansal
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=20190930075938.77a2c70d@hermes.lan \
--to=stephen@networkplumber.org \
--cc=users@dpdk.org \
--cc=zeebee48@gmail.com \
/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).