From: Yu Jiang <yux.jiang@intel.com>
To: yuan.peng@intel.com, dts@dpdk.org
Cc: Yu Jiang <yux.jiang@intel.com>
Subject: [dts] [PATCH V2 0/2] [PATCH V2] pmdrss_hash: replace legacy filter with rte_flow
Date: Mon, 8 Nov 2021 14:00:29 +0800 [thread overview]
Message-ID: <1636351231-2373-1-git-send-email-yux.jiang@intel.com> (raw)
[PATCH V2] pmdrss_hash: replace legacy filter with rte_flow
Yu Jiang (2):
test_plans/pmdrss_hash: replace legacy filter with rte_flow
tests/pmdrss_hash: replace legacy filter with rte_flow
conf/test_case_checklist.json | 11 +++-
test_plans/pmdrss_hash_test_plan.rst | 46 +++++++++++++--
tests/TestSuite_pmdrss_hash.py | 107 +++++++++++++++++------------------
3 files changed, 103 insertions(+), 61 deletions(-)
--
2.7.4
next reply other threads:[~2021-11-08 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 6:00 Yu Jiang [this message]
2021-11-08 6:00 ` [dts] [PATCH V2 1/2] test_plans/pmdrss_hash: " Yu Jiang
2021-11-08 6:00 ` [dts] [PATCH V2 2/2] tests/pmdrss_hash: " Yu Jiang
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=1636351231-2373-1-git-send-email-yux.jiang@intel.com \
--to=yux.jiang@intel.com \
--cc=dts@dpdk.org \
--cc=yuan.peng@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).