From: Feifei Wang <feifei.wang2@arm.com>
Cc: dev@dpdk.org, nd@arm.com, Feifei Wang <feifei.wang2@arm.com>
Subject: [PATCH v3 0/3] fix test-pipeline issues
Date: Tue, 12 Sep 2023 14:39:00 +0800 [thread overview]
Message-ID: <20230912063903.1266245-1-feifei.wang2@arm.com> (raw)
In-Reply-To: <20230626074538.3354554-1-feifei.wang2@arm.com>
For test-pipeline application, there are some problems with the normal
operation of the program and security issues. These patches can fix
these issues.
v3: fix SIGINT handling issue and add dev close operation
Feifei Wang (3):
app/test-pipeline: relax RSS hash requirement
app/test-pipeline: fix SIGINT handling issue
app/test-pipeline: add dev close operation
app/test-pipeline/init.c | 22 ++++-
app/test-pipeline/main.c | 33 +++++++
app/test-pipeline/main.h | 2 +
app/test-pipeline/pipeline_acl.c | 6 +-
app/test-pipeline/pipeline_hash.c | 110 ++++++++++-----------
app/test-pipeline/pipeline_lpm.c | 6 +-
app/test-pipeline/pipeline_lpm_ipv6.c | 6 +-
app/test-pipeline/pipeline_stub.c | 6 +-
app/test-pipeline/runtime.c | 132 ++++++++++++++------------
9 files changed, 198 insertions(+), 125 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2023-09-12 6:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 7:45 [PATCH] app/test-pipeline: relax RSS hash requirement Feifei Wang
2023-07-12 14:51 ` Thomas Monjalon
2023-07-14 7:50 ` lihuisong (C)
2023-07-14 8:07 ` Feifei Wang
2023-07-14 8:27 ` [PATCH v2] " Feifei Wang
2023-09-12 6:39 ` Feifei Wang [this message]
2023-09-12 6:39 ` [PATCH v3 1/3] " Feifei Wang
2023-09-12 6:39 ` [PATCH v3 2/3] app/test-pipeline: fix SIGINT handling issue Feifei Wang
2023-09-12 6:39 ` [PATCH v3 3/3] app/test-pipeline: add dev close operation Feifei Wang
2023-10-17 20:01 ` [PATCH v3 0/3] fix test-pipeline issues Thomas Monjalon
2023-10-18 13:39 ` Dumitrescu, Cristian
2023-11-23 1:54 ` Thomas Monjalon
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=20230912063903.1266245-1-feifei.wang2@arm.com \
--to=feifei.wang2@arm.com \
--cc=dev@dpdk.org \
--cc=nd@arm.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).