From: pengyuan <yuan.peng@intel.com>
To: dts@dpdk.org
Cc: pengyuan <yuan.peng@intel.com>
Subject: [dts] [PATCH] *** tests: add fortville rss granularity script ***
Date: Thu, 16 Jun 2016 09:19:38 +0800 [thread overview]
Message-ID: <1466039979-20539-1-git-send-email-yuan.peng@intel.com> (raw)
In-Reply-To: <yes>
*** fortville rss granularity ***
1. Support granularity configuration of RSS
By default Fortville uses hash input set preloaded from NVM image which includes all fields
IPv4/v6+TCP/UDP port. Potential problem for this is global configuration per device and can
affect all ports. It is required that hash input set can be configurable, such as using IPv4
only or IPv6 only or IPv4/v6+TCP/UDP.
2. support 32-bit GRE keys
By default Fortville extracts only 24 bits of GRE key to FieldVector (NVGRE use case) but
for Telco use cases full 32-bit GRE key is needed. It is required that both 24-bit and 32-bit
keys for GRE should be supported. the test plan is to test the API to switch between 24-bit and
32-bit keys
pengyuan (1):
tests: add fortville rss granularity script
.../fortville_rss_granularity_config_test_plan.rst | 340 +++++++++++
.../TestSuite_fortville_rss_granularity_config.py | 634 +++++++++++++++++++++
2 files changed, 974 insertions(+)
create mode 100644 test_plans/fortville_rss_granularity_config_test_plan.rst
create mode 100644 tests/TestSuite_fortville_rss_granularity_config.py
--
2.5.0
next prev parent reply other threads:[~2016-06-16 1:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <yes>
2016-06-15 8:12 ` [dts] [PATCH] Support fortpark_TLV pengyuan
2016-06-21 9:01 ` Liu, Yong
2016-06-15 8:46 ` [dts] [PATCH] Support NIC type fortpark_TLV pengyuan
2016-06-21 9:08 ` Liu, Yong
2016-06-16 1:19 ` pengyuan [this message]
2016-06-16 1:19 ` [dts] [PATCH] tests: add fortville rss granularity script pengyuan
2016-06-22 8:25 ` Pei, Yulong
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=1466039979-20539-1-git-send-email-yuan.peng@intel.com \
--to=yuan.peng@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).