From: Weiyuan Li <weiyuanx.li@intel.com>
To: dts@dpdk.org, yuan.peng@intel.com
Cc: Weiyuan Li <weiyuanx.li@intel.com>
Subject: [dts][PATCH V3 4/4] test_plans/vf_vlan: update dts code for driver change
Date: Mon, 11 Jul 2022 15:22:34 +0800 [thread overview]
Message-ID: <20220711072234.852-4-weiyuanx.li@intel.com> (raw)
In-Reply-To: <20220711072234.852-1-weiyuanx.li@intel.com>
The out-tree driver has vf-vlan-pruning option,but in-tree driver has not.
So we need different action to enable vlan filter when we validate the vlan filter function with in-tree and out-tree kernel drvier.
Signed-off-by: Weiyuan Li <weiyuanx.li@intel.com>
---
v2:
-fix format issue
v3:
-modify the code to check whether vf-vlan-pruning option exists.
-modify the description of the test plan about vf-vlan-pruning.
test_plans/vf_vlan_test_plan.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/test_plans/vf_vlan_test_plan.rst b/test_plans/vf_vlan_test_plan.rst
index c183b3d6..2c38d4dd 100644
--- a/test_plans/vf_vlan_test_plan.rst
+++ b/test_plans/vf_vlan_test_plan.rst
@@ -21,6 +21,10 @@ Prerequisites
0000:87:00.0 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f0 drv=i40e unused=
0000:87:00.1 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f1 drv=i40e unused=
+ If the drive support vf-vlan-pruning flag:
+ ethtool --set-priv-flags ens259f0 vf-vlan-pruning on
+ ethtool --set-priv-flags ens259f1 vf-vlan-pruning on
+
echo 1 > /sys/bus/pci/devices/0000\:87\:00.0/sriov_numvfs
echo 1 > /sys/bus/pci/devices/0000\:87\:00.1/sriov_numvfs
--
2.27.0
next prev parent reply other threads:[~2022-07-11 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 7:22 [dts][PATCH V3 1/4] tests/kernelpf_iavf: " Weiyuan Li
2022-07-11 7:22 ` [dts][PATCH V3 2/4] tests/vf_vlan: " Weiyuan Li
2022-07-11 7:22 ` [dts][PATCH V3 3/4] test_plans/kernelpf_iavf: " Weiyuan Li
2022-07-11 7:22 ` Weiyuan Li [this message]
2022-07-18 9:36 ` [dts][PATCH V3 4/4] test_plans/vf_vlan: " Chen, LingliX
2022-08-24 8:26 ` lijuan.tu
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=20220711072234.852-4-weiyuanx.li@intel.com \
--to=weiyuanx.li@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).