From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Han, YingyaX" <yingyax.han@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Han, YingyaX" <yingyax.han@intel.com>
Subject: RE: [dts][PATCH V1]test_plans/nic_single_core_perf: modify test plan to adapt meson build
Date: Sun, 17 Apr 2022 14:05:23 +0000 [thread overview]
Message-ID: <341f922850ab46b99f3a3820c528ad64@intel.com> (raw)
In-Reply-To: <20220415101220.1905362-1-yingyax.han@intel.com>
> - For FVL40g, if test 16 Byte Descriptor, need to set the
> "CONFIG_RTE_LIBRTE_I40E_16BYTE_RX_DESC=y"
> - in ./config/common_base and re-build DPDK.
>
> - For CVL25G, if test 16 Byte Descriptor, need to set the
> "CONFIG_RTE_LIBRTE_ICE_16BYTE_RX_DESC=y"
> - in ./config/common_base and re-build DPDK.
> -
> + if test 16 or 32 Byte Descriptor, please set the value of
> + "rx_desc_size" to 16 or 32 in dts/conf/nic_single_core_perf.cfg,
> + and the default value is 16.
Test plan is to introduce feature, test cases and how to test manually, not how to use automation.
If you would like to introduce that, welcome to contribute to guides in doc/gsg_dts/
prev parent reply other threads:[~2022-04-17 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 10:12 hanyingya
2022-04-17 14:05 ` 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=341f922850ab46b99f3a3820c528ad64@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=yingyax.han@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).