From: Wei Ling <weix.ling@intel.com>
To: dts@dpdk.org
Cc: Wei Ling <weix.ling@intel.com>
Subject: [dts][PATCH V2 1/2] test_plans/vf_interrupt_pmd_test_plan: remove change DPDK code steps
Date: Wed, 19 Jan 2022 15:54:27 +0800 [thread overview]
Message-ID: <20220119075427.919555-1-weix.ling@intel.com> (raw)
1.Remove change DPDK code steps.
2.Modify app name from l3fwd-power to dpdk-l3fwd-power.
Signed-off-by: Wei Ling <weix.ling@intel.com>
---
test_plans/vf_interrupt_pmd_test_plan.rst | 30 +++++++++--------------
1 file changed, 12 insertions(+), 18 deletions(-)
diff --git a/test_plans/vf_interrupt_pmd_test_plan.rst b/test_plans/vf_interrupt_pmd_test_plan.rst
index a8ed3d8e..59eae680 100644
--- a/test_plans/vf_interrupt_pmd_test_plan.rst
+++ b/test_plans/vf_interrupt_pmd_test_plan.rst
@@ -57,13 +57,10 @@ Iommu pass through feature has been enabled in kernel::
intel_iommu=on iommu=pt
-Modify the DPDK-l3fwd-power source code and recompile the l3fwd-power::
+Compile the dpdk-l3fwd-power::
- sed -i -e '/DEV_RX_OFFLOAD_CHECKSUM,/d' ./examples/l3fwd-power/main.c
-
- export RTE_TARGET=x86_64-native-linuxapp-gcc
- export RTE_SDK=`/root/DPDK`
- make -C examples/l3fwd-power
+ meson configure -Dexamples=l3fwd-power x86_64-native-linuxapp-gcc
+ ninja -C x86_64-native-linuxapp-gcc
Support igb_uio and vfio driver, if used vfio, kernel need 3.6+ and enable vt-d
in bios. When used vfio, requested to insmod two drivers vfio and vfio-pci.
@@ -79,7 +76,7 @@ Test Case1: Check Interrupt for PF with vfio driver on ixgbe and i40e
2. start l3fwd-power with PF::
- examples/l3fwd-power/build/l3fwd-power -l 1-3 -n 4 -- -P -p 0x01 --config '(0,0,2)'
+ x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -l 1-3 -n 4 -- -P -p 0x01 --config '(0,0,2)'
3. Send packet with packet generator to the pf NIC, check that thread core2 waked up::
@@ -103,7 +100,7 @@ Test Case2: Check Interrupt for PF with igb_uio driver on ixgbe and i40e
2. start l3fwd-power with PF::
- examples/l3fwd-power/build/l3fwd-power -l 1-3 -n 4 -- -P -p 0x01 --config '(0,0,2)'
+ x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -l 1-3 -n 4 -- -P -p 0x01 --config '(0,0,2)'
3. Send packet with packet generator to the pf NIC, check that thread core2 waked up::
@@ -129,7 +126,7 @@ Test Case3: Check Interrupt for VF with vfio driver on ixgbe and i40e
2. Start l3fwd-power with VF::
- examples/l3fwd-power/build/l3fwd-power -l 1-3 -n 4 -- -P -p 0x01 --config '(0,0,2)'
+ x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -l 1-3 -n 4 -- -P -p 0x01 --config '(0,0,2)'
3. Send packet with packet generator to the pf NIC, check that thread core2 waked up::
@@ -161,13 +158,10 @@ Test Case4: VF interrupt pmd in VM with vfio-pci
-device virtserialport,chardev=vm0_qga0,name=org.qemu.guest_agent.0 -vnc :11 \
-drive file=/home/image/ubuntu16-0.img,format=qcow2,if=virtio,index=0,media=disk
-3. Modify the DPDK-l3fwd-power source code and recompile the l3fwd-power::
-
- sed -i -e '/DEV_RX_OFFLOAD_CHECKSUM,/d' ./examples/l3fwd-power/main.c
+3. Compile the l3fwd-power::
- export RTE_TARGET=x86_64-native-linuxapp-gcc
- export RTE_SDK=`/root/DPDK`
- make -C examples/l3fwd-power
+ meson configure -Dexamples=l3fwd-power x86_64-native-linuxapp-gcc
+ ninja -C x86_64-native-linuxapp-gcc
4. Bind VF 0 to the vfio-pci driver::
@@ -180,7 +174,7 @@ Test Case4: VF interrupt pmd in VM with vfio-pci
5. start l3fwd-power in VM::
- examples/l3fwd-power/build/l3fwd-power -l 1-3 -n 4 -- -P -p 0x01 --config '(0,0,2)'
+ x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -l 1-3 -n 4 -- -P -p 0x01 --config '(0,0,2)'
6. Send packet with packet generator to the VM, check that thread core2 waked up::
@@ -205,7 +199,7 @@ Test Case5: vf multi-queue interrupt with vfio-pci on i40e
2. Start l3fwd-power with VF::
- examples/l3fwd-power/build/l3fwd-power -c 3f -n 4 -m 2048 -- -P -p 0x1 --config="(0,0,1),(0,1,2),(0,2,3),(0,3,4)"
+ x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -c 3f -n 4 -m 2048 -- -P -p 0x1 --config="(0,0,1),(0,1,2),(0,2,3),(0,3,4)"
3. Send UDP packets with random ip and dest mac = vf mac addr::
@@ -252,7 +246,7 @@ Test Case6: VF multi-queue interrupt in VM with vfio-pci on i40e
4.Start l3fwd-power in VM::
- ./build/l3fwd-power -l 0-3 -n 4 -m 2048 -- -P -p 0x1 --config="(0,0,0),(0,1,1),(0,2,2),(0,3,3)"
+ x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -l 0-3 -n 4 -m 2048 -- -P -p 0x1 --config="(0,0,0),(0,1,1),(0,2,2),(0,3,3)"
5. Send UDP packets with random ip and dest mac = vf mac addr::
--
2.25.1
reply other threads:[~2022-01-19 7:54 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=20220119075427.919555-1-weix.ling@intel.com \
--to=weix.ling@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).