automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: antonio.fischetti@intel.com
Subject: [dpdk-test-report] |FAILURE| pw31878 [PATCH v2] net/virtio: fix an incorrect behavior of device stop/start Re: [PATCH] [PATCH v2] net/virtio: fix an incorrect behavior> of device stop/start> > Hi Tiwei > > I'm doing some regression tests with v17.11-rc4. I ran> into a hitch with testpmd running into a guest VM. It happens> that no packet gets forwarded by testpmd.> The issue seems to appear after this patch was upstreamed.> > I saw there's a way to make it work ie by avoiding to> increment the last consumed descriptor:> > --- a/drivers/net/virtio/virtqueue.c> +++ b/drivers/net/virtio/virtqueue.c> @@ -80 7 +80 7 @@ virtqueue_flush(struct virtqueue *vq)> rte_pktmbuf_free(dxp->cookie); >                         dxp->cookie = NULL; >                 }> -               vq->vq_used_cons_idx++; > +               //vq->vq_used_cons_idx++; >                 vq_ring_free_chain(vq  desc_idx); > > Not quite sure if this change make any sense to you?> > Some details below.> > The issue appears only if the traffic generator is already> sending packets before I launch testpmd in the guest.> > In my testbench I have Open-vSwitch (OvS-DPDK) which launches> a VM with 2 vhostuserclient ports (vhu0 and vhu1) each with> a single queue.> My OvS has 2 physical ports: dpdk0 and dpdk1.> dpdk0 forwards packets back and forth from/to the generator> to/from vhu0.> Similarly dpdk1 forwards packets back and forth from/to the generator> to/from vhu1.> > In OvS there are 2 different PMD threads serving the 2> vhostuserclient ports.> > While the traffic generator is already sending packets in the> guest VM I launch> ./testpmd -c 0x3 -n 4 --socket-mem 512 -- --burst=64 -i --> txqflags=0xf00 --disable-hw-vlan> > The issue is that I see no packet received on the traffic generator> and in fact testpmd shows> > ---------------------- Forward statistics for port 0 ------------------> ----> RX-packets: 0 RX-dropped: 0 RX-total: 0> TX-packets: 0 TX-dropped: 0 TX-total: 0> ----------------------------------------------------------------------> ------> > ---------------------- Forward statistics for port 1 ----------------> ------> RX-packets: 0 RX-dropped: 0 RX-total: 0> TX-packets: 0 TX-dropped: 0 TX-total: 0> ----------------------------------------------------------------------> ------> > +++++++++++++++ Accumulated forward statistics for all> ports+++++++++++++++> RX-packets: 0 RX-dropped: 0 RX-total: 0> TX-packets: 0 TX-dropped: 0 TX-total: 0> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++> ++++> > Please let me know if I missed something or if you need> more info on my testbench.> > > Thanks > Antonio> > > -----Original Message-----> >
Date: 01 Dec 2017 09:31:12 -0800	[thread overview]
Message-ID: <9d048a$158r5gr@fmsmga002.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1715 bytes --]

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/31878

_apply patch file failure_

Submitter: Antonio Fischetti <antonio.fischetti@intel.com>
Date: Fri, 1 Dec 2017 17:17:58 +0000  Fri Oct 20 10:09:28 2017 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:d84aad650401a122cb75bd5811e49b03ef3dc49d
                   Repo:dpdk-next-crypto, Branch:master, CommitID:224374cc0e3ca44af5141fb7035a97f338d00c18
                   Repo:dpdk-next-net, Branch:master, CommitID:607d383d3cc56d7666584f5b1b7625e385b592c4
                   Repo:dpdk-next-virtio, Branch:master, CommitID:4f761c94b520ce71c56be1c913e54a4179b81c43
                   Repo:dpdk, Branch:master, CommitID:224374cc0e3ca44af5141fb7035a97f338d00c18
                   
Apply patch file failed:
Repo: dpdk
31878:
patching file drivers/net/virtio/virtqueue.c
Hunk #1 FAILED at 80.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/virtio/virtqueue.c.rej

Repo: dpdk-next-crypto
31878:
patching file drivers/net/virtio/virtqueue.c
Hunk #1 FAILED at 80.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/virtio/virtqueue.c.rej

Repo: dpdk-next-net
31878:
patching file drivers/net/virtio/virtqueue.c
Hunk #1 FAILED at 80.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/virtio/virtqueue.c.rej

Repo: dpdk-next-virtio
31878:
patching file drivers/net/virtio/virtqueue.c
Hunk #1 FAILED at 80.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/virtio/virtqueue.c.rej

Repo: dpdk-next-eventdev
31878:
patching file drivers/net/virtio/virtqueue.c
Hunk #1 FAILED at 80.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/virtio/virtqueue.c.rej


DPDK STV team

                 reply	other threads:[~2017-12-01 17:31 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='9d048a$158r5gr@fmsmga002.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=antonio.fischetti@intel.com \
    --cc=test-report@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).