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 v1] test_plans: update traffic mac addr of TG for ntb cases
Date: Fri, 21 Feb 2020 02:03:12 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BBCC938@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200219204524.103642-1-yinan.wang@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Yinan
> Sent: Thursday, February 20, 2020 4:45 AM
> To: dts@dpdk.org
> Cc: Wang, Yinan <yinan.wang@intel.com>
> Subject: [dts] [PATCH v1] test_plans: update traffic mac addr of TG for ntb
> cases
>
> From: Wang Yinan <yinan.wang@intel.com>
>
> Signed-off-by: Wang Yinan <yinan.wang@intel.com>
> ---
> test_plans/ntb_test_plan.rst | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/test_plans/ntb_test_plan.rst b/test_plans/ntb_test_plan.rst index
> 415efe6..edef78d 100644
> --- a/test_plans/ntb_test_plan.rst
> +++ b/test_plans/ntb_test_plan.rst
> @@ -108,11 +108,13 @@ Test Case1: NTB test with file-trans fwd mode
> using igb_uio
>
> ./examples/ntb/build/ntb_fwd -l 28-32 -n 6 -- -i --buf-size=65407
> >set fwd file-trans
> + >start
>
> 3. Launch ntb_fwd sample on Machine2::
>
> ./examples/ntb/build/ntb_fwd -l 28-32 -n 6 -- -i --buf-size=65407
> >set fwd file-trans
> + >start
>
> 4. Send file from Machine1::
>
> @@ -173,7 +175,7 @@ Test Case3: NTB test with rxonly/txonly fwd mode
> using igb_uio 4. Check throughput with log info on two machines.
>
> Test Case4: NTB test with rxonly/txonly fwd mode using vfio-pci -
> ===============================================================
> +==============================================================
>
> 1. Insmod kernel module and bind Non-Transparent Bridge to vfio-pci driver
> on two host machines separately::
>
> @@ -224,7 +226,7 @@ Test flow: TG <-> NIC1 <-> NTB1 <-> NTB2 <-> NIC2 <->
> TG
> >start
> >show port stats
>
> -4. Check throughput with log info on two machines.
> +4. Send packets (dest mac= nic mac address) with TG and check throughput
> with log info on two machines.
>
> Test Case6: NTB test with io fwd mode using vfio-pci
> ====================================================
> @@ -254,4 +256,4 @@ Test flow: TG <-> NIC1 <-> NTB1 <-> NTB2 <-> NIC2 <->
> TG
> >start
> >show port stats
>
> -4. Check throughput with log info on two machines.
> \ No newline at end of file
> +4. Send packets (dest mac= nic mac address) with TG and check throughput
> with log info on two machines.
> --
> 2.17.1
prev parent reply other threads:[~2020-02-21 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 20:45 Yinan
2020-02-21 2:03 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BBCC938@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).