From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Mo, YufengX" <yufengx.mo@intel.com>
Subject: Re: [dts] [PATCH V1 2/4] [next]config/ports: add trex format comment
Date: Thu, 8 Aug 2019 05:41:40 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAFF5D9@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1564364921-33333-3-git-send-email-yufengx.mo@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yufengmx
> Sent: Monday, July 29, 2019 9:49 AM
> To: dts@dpdk.org
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts] [PATCH V1 2/4] [next]config/ports: add trex format comment
>
>
> add trex format comment as TREX:x
>
> Signed-off-by: yufengmx <yufengx.mo@intel.com>
> ---
> conf/ports.cfg | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/conf/ports.cfg b/conf/ports.cfg index 7fa7aae..1102375 100644
> --- a/conf/ports.cfg
> +++ b/conf/ports.cfg
> @@ -4,6 +4,7 @@
> # pci=Pci BDF,intf=Kernel interface;
> # pci=Pci BDF,mac=Mac address,peer=Tester Pci BDF,numa=Port Numa
> # pci=Pci BDF,peer=IXIA:card.port
> +# pci=Pci BDF,peer=TREX:port
> # pci=Pci BDF,peer=Tester Pci BDF,tp_ip=$(IP),tp_path=$({PERL_PATH);
> # pci=Pci BDF,peer=Tester Pci BDF,sec_port=yes,first_port=Pci BDF;
> # [VM NAME] virtual machine name; This section is for virutal scenario @@ -
> 14,6 +15,7 @@ ports =
> pci=XX:XX.X,intf=eth0;
> pci=YY:YY.Y,mac=XX:XX:XX:XX:XX:XX,peer=ZZ:ZZ.Z,numa=0;
> pci=ZZ:ZZ.Y,peer=IXIA:X.Y;
> + pci=ZZ:ZZ.Y,peer=TREX:X;
>
> pci=0000:XX:XX.X,peer=0000:ZZ:ZZ.Z,tp_ip=127.0.0.1,tp_path=/home/libertyTr
> ailTP_322291/perl;
> pci=0000:YY:YY.Y,peer=0000:ZZ:ZZ.Z,sec_port=yes,first_port=XX:XX.X;
> [VM NAME]
> --
> 1.9.3
next prev parent reply other threads:[~2019-08-08 5:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 1:48 [dts] [PATCH V1 0/4] dts: update suite nic_single_core_perf and ports config yufengmx
2019-07-29 1:48 ` [dts] [PATCH V1 1/4] [next]config/nic_single_core_perf: fix file format issue yufengmx
2019-07-29 1:48 ` [dts] [PATCH V1 2/4] [next]config/ports: add trex format comment yufengmx
2019-08-08 5:41 ` Tu, Lijuan [this message]
2019-07-29 1:48 ` [dts] [PATCH V1 3/4] [next]framework/dut: add check condition for trex port yufengmx
2019-08-08 5:41 ` Tu, Lijuan
2019-07-29 1:48 ` [dts] [PATCH V1 4/4] [next]tests/nic_single_core_perf: update script yufengmx
2019-08-08 5:41 ` Tu, Lijuan
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=8CE3E05A3F976642AAB0F4675D0AD20E0BAFF5D9@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=yufengx.mo@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).