test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: Fangfang Wei <fangfangx.wei@intel.com>, dts@dpdk.org
Subject: Re: [dts] [PATCH V1] tests/sriov_kvm: fix can't receive packets failure
Date: Mon, 28 Aug 2017 17:48:25 +0800	[thread overview]
Message-ID: <59A3E6E9.4090800@intel.com> (raw)
In-Reply-To: <1503652743-92955-1-git-send-email-fangfangx.wei@intel.com>

Fangfang,
Please make your description more clear, which kind of buffer will be 
full in which kind of situation?

Thanks,
Marvin

On 08/25/2017 05:19 PM, Fangfang Wei wrote:
> 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
> buffer is full on host.
> Set fwd rxonly and then start forward on host testpmd, buffer will not full.
>
> 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')

      reply	other threads:[~2017-08-28  1:05 UTC|newest]

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

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=59A3E6E9.4090800@intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@dpdk.org \
    --cc=fangfangx.wei@intel.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).