test suite reviews and discussions
 help / color / mirror / Atom feed
From: Lingli Chen <linglix.chen@intel.com>
To: dts@dpdk.org
Cc: Lingli Chen <linglix.chen@intel.com>
Subject: [dts][PATCH V1 5/7] test_plans/vhost_virtio_user_interrupt: Delete modify l3fwd-power example code
Date: Tue, 16 Nov 2021 14:51:28 +0000	[thread overview]
Message-ID: <20211116145130.113807-6-linglix.chen@intel.com> (raw)
In-Reply-To: <20211116145130.113807-1-linglix.chen@intel.com>

Delete Prerequisites

Signed-off-by: Lingli Chen <linglix.chen@intel.com>
---
 .../vhost_virtio_user_interrupt_test_plan.rst | 20 -------------------
 1 file changed, 20 deletions(-)

diff --git a/test_plans/vhost_virtio_user_interrupt_test_plan.rst b/test_plans/vhost_virtio_user_interrupt_test_plan.rst
index 2ac6a385..e70ec91f 100644
--- a/test_plans/vhost_virtio_user_interrupt_test_plan.rst
+++ b/test_plans/vhost_virtio_user_interrupt_test_plan.rst
@@ -39,26 +39,6 @@ to virtio side, check virtio-user cores can be wakeup status, and virtio-user co
 status after stop sending packets from traffic generator.This test plan cover both vhost-net and
 vhost-user as the backend.
 
-Prerequisites
-=============
-
-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 Case1: Split ring virtio-user interrupt test with vhost-user as backend
 ============================================================================
 
-- 
2.33.1


  parent reply	other threads:[~2021-11-16  6:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 14:51 [dts][PATCH V1 0/7] " Lingli Chen
2021-11-16 14:51 ` [dts][PATCH V1 1/7] test_plans/vhost_event_idx_interrupt: " Lingli Chen
2021-11-16 14:51 ` [dts][PATCH V1 2/7] tests/vhost_event_idx_interrupt: " Lingli Chen
2021-11-16 14:51 ` [dts][PATCH V1 3/7] test_plans/vhost_virtio_pmd_interrupt: " Lingli Chen
2021-11-16 14:51 ` [dts][PATCH V1 4/7] tests/vhost_virtio_pmd_interrupt: " Lingli Chen
2021-11-22  3:21   ` Wang, Yinan
2021-11-16 14:51 ` Lingli Chen [this message]
2021-11-16 14:51 ` [dts][PATCH V1 6/7] tests/vhost_virtio_user_interrupt: " Lingli Chen
2021-11-22  3:21   ` Wang, Yinan
2021-11-16 14:51 ` [dts][PATCH V1 7/7] tests/vhost_user_interrupt: " Lingli Chen
2021-11-16  6:55   ` Chen, LingliX
2021-11-22  3:21     ` Wang, Yinan
2021-11-22 14:48       ` 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=20211116145130.113807-6-linglix.chen@intel.com \
    --to=linglix.chen@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).