From: "Xu, Qian Q" <qian.q.xu@intel.com>
To: "Xu, HuilongX" <huilongx.xu@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>, "Liu, Yong" <yong.liu@intel.com>
Cc: "Xu, HuilongX" <huilongx.xu@intel.com>
Subject: Re: [dts] [PATCH V1 1/6] add a new config file for fortvill PF full function test
Date: Wed, 6 Sep 2017 05:07:15 +0000 [thread overview]
Message-ID: <82F45D86ADE5454A95A89742C8D1410E3B7624C0@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1503646931-91671-1-git-send-email-huilongx.xu@intel.com>
Hi, Marvin
Do you have comments on this?
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of xu,huilong
> Sent: Friday, August 25, 2017 3:42 PM
> To: dts@dpdk.org
> Cc: Xu, HuilongX <huilongx.xu@intel.com>
> Subject: [dts] [PATCH V1 1/6] add a new config file for fortvill PF full function
> test
>
> Signed-off-by: xu,huilong <huilongx.xu@intel.com>
> ---
> executions/execution_fortville_full.cfg | 60
> +++++++++++++++++++++++++++++++++
> 1 file changed, 60 insertions(+)
> create mode 100644 executions/execution_fortville_full.cfg
>
> diff --git a/executions/execution_fortville_full.cfg
> b/executions/execution_fortville_full.cfg
> new file mode 100644
> index 0000000..0d3a4b7
> --- /dev/null
> +++ b/executions/execution_fortville_full.cfg
> @@ -0,0 +1,60 @@
> +[Execution1]
> +crbs=<CRB IP Address>
> +drivername=<driver name igb_uio or vfio-pci or mlx5_core> rx_mode=full
> +test_suites=
> + blacklist,
> + checksum_offload,
> + cmdline,
> + coremask,
> + distributor,
> + dual_vlan,
> + dynamic_config,
> + efd,
> + external_mempool_handler,
> + fdir,
> + fortville_rss_granularity_config,
> + generic_filter,
> + hello_world,
> + hot_plug,
> + ieee1588,
> + ipfrag,
> + ipgre,
> + ipv4_reassembly,
> + jumboframes,
> + keep_alive,
> + kni,
> + l2fwd,
> + link_flowctrl,
> + link_status_interrupt,
> + mac_filter,
> + mempool_exthandler,
> + multiprocess,
> + netmap_compat,
> + nvgre,
> + pmd,
> + pmd_bonded,
> + pmdpcap,
> + pmdrss_hash,
> + pmdrssreta,
> + ptpclient,
> + ptype_mapping,
> + qinq_filter,
> + queue_start_stop,
> + quota_watermark,
> + rxtx_callbacks,
> + scatter,
> + short_live,
> + shutdown_api,
> + skeleton,
> + timer,
> + tso,
> + tx_preparation,
> + uni_pkt,
> + userspace_ethtool,
> + vlan,
> + vlan_ethertype_config,
> + vxlan
> +targets=
> + x86_64-native-linuxapp-gcc
> +parameters=nic_type=cfg:func=true
> --
> 1.9.3
next prev parent reply other threads:[~2017-09-06 5:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 7:42 xu,huilong
2017-08-25 7:42 ` [dts] [PATCH V1 2/6] add a new config file for fortville PF scalare rx mode test xu,huilong
2017-08-25 7:42 ` [dts] [PATCH V1 3/6] add a new config file for fortville PF no vector pmd " xu,huilong
2017-08-25 7:42 ` [dts] [PATCH V1 4/6] remove old config file for fortville test xu,huilong
2017-08-25 7:42 ` [dts] [PATCH V1 5/6] add a new config file for unit test xu,huilong
2017-08-25 7:42 ` [dts] [PATCH V1 6/6] add a new example for performance test xu,huilong
2017-09-06 5:07 ` Xu, Qian Q [this message]
2017-09-06 14:59 ` [dts] [PATCH V1 1/6] add a new config file for fortvill PF full function test 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=82F45D86ADE5454A95A89742C8D1410E3B7624C0@shsmsx102.ccr.corp.intel.com \
--to=qian.q.xu@intel.com \
--cc=dts@dpdk.org \
--cc=huilongx.xu@intel.com \
--cc=yong.liu@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).