test suite reviews and discussions
 help / color / mirror / Atom feed
From: Yinan Wang <yinan.wang@intel.com>
To: dts@dpdk.org
Cc: Yinan Wang <yinan.wang@intel.com>
Subject: [dts]  [PATCH v1] test_plans/vdev_primary_secondary_test_plan.rst
Date: Thu, 20 Aug 2020 12:17:34 -0400	[thread overview]
Message-ID: <20200820161734.25041-1-yinan.wang@intel.com> (raw)

Add prerequisites l3fwd-power code change before test

Signed-off-by: Yinan Wang <yinan.wang@intel.com>
---
 test_plans/vdev_primary_secondary_test_plan.rst | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/test_plans/vdev_primary_secondary_test_plan.rst b/test_plans/vdev_primary_secondary_test_plan.rst
index 8cb1405..33d240e 100644
--- a/test_plans/vdev_primary_secondary_test_plan.rst
+++ b/test_plans/vdev_primary_secondary_test_plan.rst
@@ -53,6 +53,22 @@ Prerequisites
 Assuming that DPDK build has been set up and the multi-process sample
 applications have been built. It is also assumed that a traffic generator has
 been configured and plugged in to the NIC ports 0 and 1.
+Also need modify l3fwd-power example code and recompile::
+
+        --- a/examples/l3fwd-power/main.c
+        +++ b/examples/l3fwd-power/main.c
+        @@ -245,10 +245,9 @@ uint16_t nb_lcore_params = RTE_DIM(lcore_params_array_default);
+
+         static struct rte_eth_conf port_conf = {
+                .rxmode = {
+        -               .mq_mode        = ETH_MQ_RX_RSS,
+        +               .mq_mode        = ETH_MQ_RX_NONE,
+                        .max_rx_pkt_len = RTE_ETHER_MAX_LEN,
+                        .split_hdr_size = 0,
+        -               .offloads = DEV_RX_OFFLOAD_CHECKSUM,
+                },
+                .rx_adv_conf = {
+                        .rss_conf = {
 
 Test Methodology
 ----------------
-- 
2.17.1


             reply	other threads:[~2020-08-20  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20 16:17 Yinan Wang [this message]
2020-08-27  2:01 ` 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=20200820161734.25041-1-yinan.wang@intel.com \
    --to=yinan.wang@intel.com \
    --cc=dts@dpdk.org \
    /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).