test suite reviews and discussions
 help / color / mirror / Atom feed
From: Fangfang Wei <fangfangx.wei@intel.com>
To: dts@dpdk.org
Cc: Fangfang Wei <fangfangx.wei@intel.com>
Subject: [dts] [PATCH V2] tests/sriov_kvm: fix can't receive packets failure
Date: Mon, 28 Aug 2017 12:08:29 +0800	[thread overview]
Message-ID: <1503893309-94670-1-git-send-email-fangfangx.wei@intel.com> (raw)

Fix DPDK-3276: reopen set port 0 vf rxmode BAM on failed

When reopen set port 0 vf rxmode BAM on, vm can't receive packets, because
RX buffer is full on host when host receives too many packets if host only
run testpmd without "start" command.

RX buffer will be cleaned just when start forward packets.
If we not run "start", rx buffer will be full, and can't receive new packets.
In this case, we don't want pf forwarding packets, so we set fwd rxonly, and
start forwarding on host.

Signed-off-by: Fangfang Wei <fangfangx.wei@intel.com>
---
 tests/TestSuite_sriov_kvm.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/tests/TestSuite_sriov_kvm.py b/tests/TestSuite_sriov_kvm.py
index b1c3db6..8424b22 100644
--- a/tests/TestSuite_sriov_kvm.py
+++ b/tests/TestSuite_sriov_kvm.py
@@ -351,6 +351,8 @@ class TestSriovKvm(TestCase):
                                                        'vf1': self.sriov_vfs_port[1].pci}
                 self.host_testpmd.start_testpmd(
                     "1S/2C/2T", "--rxq=4 --txq=4 --txqflags=0", eal_param=eal_param)
+                self.host_testpmd.execute_cmd('set fwd rxonly')
+                self.host_testpmd.execute_cmd('start')
 
             # set up VM0 ENV
             self.vm0 = QEMUKvm(self.dut, 'vm0', 'sriov_kvm')
-- 
2.7.4

             reply	other threads:[~2017-08-28  4:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28  4:08 Fangfang Wei [this message]
2017-08-28 21:46 ` Liu, Yong

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=1503893309-94670-1-git-send-email-fangfangx.wei@intel.com \
    --to=fangfangx.wei@intel.com \
    --cc=dts@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).