DPDK patches and discussions
 help / color / mirror / Atom feed
From: Wisam Monther <wisamm@nvidia.com>
To: "arybchenko@solarflare.com" <arybchenko@solarflare.com>,
	NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
	Alexander Kozyrev <akozyrev@nvidia.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: [dpdk-dev] [PATCH] app/flow-perf: fix setting decap data for decap actions
Date: Wed, 10 Mar 2021 09:45:47 +0000	[thread overview]
Message-ID: <MWHPR12MB167739B112AC13E536CA3B5AA4919@MWHPR12MB1677.namprd12.prod.outlook.com> (raw)

When using decap actions it's been set to the data to decap
into the encap_data instead of decap_data, as a results we end
up with bad encap and decap data in many cases.

Fixes: 0c8f1f4ab90e ("app/flow-perf: support raw encap/decap actions")
Cc: stable@dpdk.org<mailto:stable@dpdk.org>

Signed-off-by: Wisam Jaddo <wisamm@nvidia.com<mailto:wisamm@nvidia.com>>
---
app/test-flow-perf/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app/test-flow-perf/main.c b/app/test-flow-perf/main.c
index 99d0463456..e3e6a1b420 100644
--- a/app/test-flow-perf/main.c
+++ b/app/test-flow-perf/main.c
@@ -726,7 +726,7 @@ args_parse(int argc, char **argv)
                                        for (i = 0; i < RTE_DIM(flow_options); i++) {
                                                if (strcmp(flow_options[i].str, token) == 0) {
                                                        printf("%s,", token);
-                                                       encap_data |= flow_options[i].mask;
+                                                       decap_data |= flow_options[i].mask;
                                                        break;
                                                }
                                                /* Reached last item with no match */
--
2.17.1

                 reply	other threads:[~2021-03-10  9:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=MWHPR12MB167739B112AC13E536CA3B5AA4919@MWHPR12MB1677.namprd12.prod.outlook.com \
    --to=wisamm@nvidia.com \
    --cc=akozyrev@nvidia.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).