From: Tiwei Bie <tiwei.bie@intel.com>
To: "Fischetti, Antonio" <antonio.fischetti@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"yliu@fridaylinux.org" <yliu@fridaylinux.org>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"jfreimann@redhat.com" <jfreimann@redhat.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] net/virtio: fix an incorrect behavior of device stop/start
Date: Mon, 4 Dec 2017 15:19:35 +0800 [thread overview]
Message-ID: <20171204071935.semcmhb2agdkbggp@debian-xvivbkq> (raw)
In-Reply-To: <20171202043033.gwg3lx2hlmdway3x@debian-xvivbkq>
On Sat, Dec 02, 2017 at 12:30:33PM +0800, Tiwei Bie wrote:
> Hi Antonio,
>
> On Sat, Dec 02, 2017 at 01:17:58AM +0800, Fischetti, Antonio wrote:
> > Hi All,
> > I've got an update on this.
> > I could replicate the same issue by using testpmd + a VM (= Virtual Machine).
> >
> > The test topology I'm using is:
> >
> >
> > [Traffic gen]----[NIC port #0]----[testpmd]----[vhost port #2]----+
> > |
> > |
> > [testpmd in
> > the VM]
> > |
> > |
> > [Traffic gen]----[NIC port #1]----[testpmd]----[vhost port #3]----+
> >
> >
> > So there's no OvS now in the picture: one testpmd running on the host
> > and one testpmd running on the VM.
> >
> > The issue is that no packet goes through testpmd in the VM.
> > It seems this is happening after this patch was upstreamed.
> >
> > Please note
> > -----------
> > To replicate this issue both the next 2 conditions must be met:
> > - the traffic is already being sent before launching testpmd in the VM
> > - there are at least 2 forwarding lcores.
> >
>
[...]
>
> Do you see anything I missed? Or can you reproduce the issue with the
> setup I'm using?
>
Hi Antonio,
Are you using vector Rx in your test? After some further
investigations, I found that the vector Rx could be broken
if backend has consumed all the avail descs before the
device is started. Because in current implementation, the
vector Rx will return immediately without refilling the
avail ring if the used ring is empty. So we have to refill
the avail ring after flushing the elements in the used ring.
Best regards,
Tiwei Bie
next prev parent reply other threads:[~2017-12-04 7:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 8:26 [dpdk-stable] [PATCH] " Tiwei Bie
[not found] ` <20170830091306.a5whdd7xrgb4jbtn@dhcp-192-218.str.redhat.com>
2017-08-30 10:24 ` [dpdk-stable] [dpdk-dev] " Tiwei Bie
[not found] ` <20170901062646.iek4azi6nez7vyrr@dhcp-192-218.str.redhat.com>
2017-09-01 7:14 ` Tiwei Bie
2017-10-19 13:53 ` Yuanhan Liu
2017-10-20 2:09 ` [dpdk-stable] [PATCH v2] " Tiwei Bie
2017-10-20 5:35 ` Yuanhan Liu
2017-11-14 17:38 ` [dpdk-stable] [dpdk-dev] " Fischetti, Antonio
2017-12-01 17:17 ` Fischetti, Antonio
2017-12-02 4:30 ` Tiwei Bie
2017-12-04 7:19 ` Tiwei Bie [this message]
2017-12-04 11:46 ` Fischetti, Antonio
2017-12-05 3:11 ` Tiwei Bie
2017-12-05 8:52 ` Fischetti, Antonio
2017-12-02 1:24 ` Tiwei Bie
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=20171204071935.semcmhb2agdkbggp@debian-xvivbkq \
--to=tiwei.bie@intel.com \
--cc=antonio.fischetti@intel.com \
--cc=dev@dpdk.org \
--cc=jfreimann@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=stable@dpdk.org \
--cc=yliu@fridaylinux.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).