From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Wang, Yinan" <yinan.wang@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Wang, Yinan" <yinan.wang@intel.com>
Subject: Re: [dts] [PATCH v2] test_plans: add large packet payload check for vm2vm_virtio_pmd_test_plan
Date: Wed, 26 Jun 2019 07:20:58 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAC50A3@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20190618003947.15521-1-yinan.wang@intel.com>
Hi Yinan,
Could you please rework your patch? applied failed.
Applying: test_plans: add large packet payload check for vm2vm_virtio_pmd_test_plan
error: patch failed: test_plans/vm2vm_virtio_pmd_test_plan.rst:78
error: test_plans/vm2vm_virtio_pmd_test_plan.rst: patch does not apply
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Yinan
> Sent: Tuesday, June 18, 2019 8:40 AM
> To: dts@dpdk.org
> Cc: Wang, Yinan <yinan.wang@intel.com>
> Subject: [dts] [PATCH v2] test_plans: add large packet payload check for
> vm2vm_virtio_pmd_test_plan
>
> From: Wang Yinan <yinan.wang@intel.com>
>
> Signed-off-by: Wang Yinan <yinan.wang@intel.com>
> ---
> test_plans/vm2vm_virtio_pmd_test_plan.rst | 24 +++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/test_plans/vm2vm_virtio_pmd_test_plan.rst
> b/test_plans/vm2vm_virtio_pmd_test_plan.rst
> index 3666751..bb9fc21 100644
> --- a/test_plans/vm2vm_virtio_pmd_test_plan.rst
> +++ b/test_plans/vm2vm_virtio_pmd_test_plan.rst
> @@ -78,8 +78,8 @@ Test Case 1: VM2VM vhost-user/virtio-pmd with
> mergeable path 3. On VM1, bind vdev with igb_uio driver,then run testpmd,
> set rxonly mode for virtio1::
>
> ./testpmd -c 0x3 -n 4 -- -i --tx-offloads=0x00 --enable-hw-vlan-strip --
> txd=1024 --rxd=1024
> - testpmd>set fwd rxonly
> - testpmd>start
> + testpmd>set fwd rxonly
> + testpmd>start
>
> 4. On VM2, bind vdev with igb_uio driver,then run testpmd, set txonly for
> virtio2 and send 64B packets::
>
> @@ -129,8 +129,8 @@ Test Case 2: VM2VM vhost-user/virtio-pmd with
> vector path 3. On VM1, bind vdev with igb_uio driver,then run testpmd, set
> rxonly for virtio1::
>
> ./testpmd -c 0x3 -n 4 -- -i --txd=1024 --rxd=1024
> - testpmd>set fwd rxonly
> - testpmd>start
> + testpmd>set fwd rxonly
> + testpmd>start
>
> 4. On VM2, bind vdev with igb_uio driver,then run testpmd, set txonly for
> virtio2 and send 64B packets::
>
> @@ -180,8 +180,8 @@ Test Case 3: VM2VM vhost-user/virtio-pmd with
> normal path 3. On VM1, bind vdev with igb_uio driver,then run testpmd, set
> rxonly for virtio1 ::
>
> ./testpmd -c 0x3 -n 4 -- -i --tx-offloads=0x00 --enable-hw-vlan-strip --
> txd=1024 --rxd=1024
> - testpmd>set fwd rxonly
> - testpmd>start
> + testpmd>set fwd rxonly
> + testpmd>start
>
> 4. On VM2, bind vdev with igb_uio driver,then run testpmd, set rxonly for
> virtio2 and send 64B packets ::
>
> @@ -231,8 +231,8 @@ Test Case 4: VM2VM vhost-user/virtio1.0-pmd with
> mergeable path 3. On VM1, bind vdev with igb_uio driver,then run testpmd,
> set rxonly for virtio1 ::
>
> ./testpmd -c 0x3 -n 4 -- -i --tx-offloads=0x00 --enable-hw-vlan-strip --
> txd=1024 --rxd=1024
> - testpmd>set fwd rxonly
> - testpmd>start
> + testpmd>set fwd rxonly
> + testpmd>start
>
> 4. On VM2, bind vdev with igb_uio driver,then run testpmd, set txonly for
> virtio2 ::
>
> @@ -292,8 +292,8 @@ Test Case 5: VM2VM vhost-user/virtio-pmd
> mergeable path with payload valid check 4. Bind virtio with igb_uio
> driver,then run testpmd, set rxonly mode for virtio-pmd on VM1::
>
> ./testpmd -c 0x3 -n 4 --file-prefix=test -- -i --txd=1024 --rxd=1024 --max-
> pkt-len=9600
> - testpmd>set fwd rxonly
> - testpmd>start
> + testpmd>set fwd rxonly
> + testpmd>start
>
> 5. Bootup pdump in VM1::
>
> @@ -355,8 +355,8 @@ Test Case 6: VM2VM vhost-user/virtio1.0-pmd
> mergeable path with payload valid ch 4. Bind virtio with igb_uio driver,then
> run testpmd, set rxonly mode for virtio-pmd on VM1::
>
> ./testpmd -c 0x3 -n 4 --file-prefix=test -- -i --txd=1024 --rxd=1024 --max-
> pkt-len=9600
> - testpmd>set fwd rxonly
> - testpmd>start
> + testpmd>set fwd rxonly
> + testpmd>start
>
> 5. Bootup pdump in VM1::
>
> --
> 2.17.1
prev parent reply other threads:[~2019-06-26 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 0:39 Yinan
2019-06-26 7:20 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0BAC50A3@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=yinan.wang@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).