DPDK usage discussions
 help / color / mirror / Atom feed
From: Venumadhav Josyula <vjosyula@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Drops seems with virtio PMD driver
Date: Thu, 29 Aug 2019 20:12:54 +0530	[thread overview]
Message-ID: <CA+i0PGVgg6cGfHCVj2WqdA+Dm2VHUn=CGU=+N1St98CCyg6mPg@mail.gmail.com> (raw)
In-Reply-To: <20190829074001.578153a8@hermes.lan>

Hi Stephen,
 >Are you using KVM?
Yes
>Did you enable virtio net acceleration?
Will get back to you. Can you let me what are benefits of it ?

Thanks,
Regards
Venu

On Thu, 29 Aug 2019 at 20:10, Stephen Hemminger <stephen@networkplumber.org>
wrote:

> On Thu, 29 Aug 2019 10:12:27 +0530
> Venumadhav Josyula <vjosyula@gmail.com> wrote:
>
> > Hi All,
> >
> > We are observing packet drops ~@90Mbs with virtio pmd driver. These
> packets
> > are not been
> > queued in the tx descriptors, the function 'rte_eth_tx_burst' is
> returning
> > the less than n.
> >
> > So questions are following
> > i)  are there any issues seen ?
> >
> > Observations in our case :-
> > i) packets are dropped and tx packets donot get incremented.
> > ii) i) happens for 30 secs after that it recovers.
> > iii) After sometime we see this issue in i) & ii) again.
> >
> > Any clues / pointers will help.
> >
> > Thanks,
> > Regards,
> > Venu
>
> The number of transmit descriptors is fixed.
> If you are producing packets faster than the other consume them then the
> transmit descriptor ring gets full. So the problem is probably on the other
> side of your virtio. Are you using KVM? Did you enable virtio net
> acceleration?
>

  reply	other threads:[~2019-08-29 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29  4:42 Venumadhav Josyula
2019-08-29 14:40 ` Stephen Hemminger
2019-08-29 14:42   ` Venumadhav Josyula [this message]
2019-08-29 14:56     ` Stephen Hemminger

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='CA+i0PGVgg6cGfHCVj2WqdA+Dm2VHUn=CGU=+N1St98CCyg6mPg@mail.gmail.com' \
    --to=vjosyula@gmail.com \
    --cc=stephen@networkplumber.org \
    --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).