From: "Li, WenjieX A" <wenjiex.a.li@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Cc: "Li, WenjieX A" <wenjiex.a.li@intel.com>
Subject: Re: [dts] [PATCH V1 2/3] test_plans: fix build error/warning
Date: Tue, 30 Apr 2019 07:47:30 +0000 [thread overview]
Message-ID: <8688172CD5C0B74590FAE19D9579F94B536DDC3C@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1556610372-16013-2-git-send-email-wenjiex.a.li@intel.com>
Tested-by: Li, WenjieX A <wenjiex.a.li@intel.com>
> -----Original Message-----
> From: Li, WenjieX A
> Sent: Tuesday, April 30, 2019 3:46 PM
> To: dts@dpdk.org
> Cc: Li, WenjieX A <wenjiex.a.li@intel.com>
> Subject: [dts][PATCH V1 2/3] test_plans: fix build error/warning
>
> fix build error/warning
>
> Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
> ---
> test_plans/vhost_enqueue_interrupt_test_plan.rst | 14 +++--
> test_plans/vhost_event_idx_interrupt_test_plan.rst | 16 ++---
> .../vhost_virtio_pmd_interrupt_test_plan.rst | 14 ++---
> .../virtio_ipsec_cryptodev_func_test_plan.rst | 72 ++++++++++++++--------
> .../virtio_perf_cryptodev_func_test_plan.rst | 44 ++++++++-----
> 5 files changed, 99 insertions(+), 61 deletions(-)
>
> diff --git a/test_plans/vhost_enqueue_interrupt_test_plan.rst
> b/test_plans/vhost_enqueue_interrupt_test_plan.rst
> index de482b3..93ff7cb 100644
> --- a/test_plans/vhost_enqueue_interrupt_test_plan.rst
> +++ b/test_plans/vhost_enqueue_interrupt_test_plan.rst
> @@ -50,9 +50,10 @@ Test Case1: Wake up vhost-user core with l3fwd-power
> sample
>
> 1. Launch virtio-user with server mode::
>
> - ./testpmd -l 7-8 -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci --file-
> prefix=virtio --
> vdev=net_virtio_user0,mac=00:11:22:33:44:10,path=/tmp/sock0,server=1,queu
> es=1 -- -i
> + ./testpmd -l 7-8 -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci --file-
> prefix=virtio \
> +
> + --vdev=net_virtio_user0,mac=00:11:22:33:44:10,path=/tmp/sock0,server=1
> + ,queues=1 -- -i
>
> -2. Build l3fwd-power sample and launch l3fwd-power with a virtual vhost
> device::
> +2. Build l3fwd-power sample and launch l3fwd-power with a virtual vhost
> device::
>
> ./l3fwd-power -l 0-3 -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci \
> --vdev 'eth_vhost0,iface=/tmp/sock0,queues=1,client=1' -- -p 0x1 --parse-
> ptype 1 --config "(0,0,2)"
> @@ -69,12 +70,13 @@ Test Case2: Wake up vhost-user cores with l3fwd-
> power sample when multi queues
>
> 1. Launch virtio-user with server mode::
>
> - ./testpmd -l 1-5 -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci --file-
> prefix=virtio --
> vdev=net_virtio_user0,mac=00:11:22:33:44:10,path=/tmp/sock0,server=1,queu
> es=4 -- -i --rxq=4 --txq=4 --rss-ip
> + ./testpmd -l 1-5 -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci --file-
> prefix=virtio \
> +
> + --vdev=net_virtio_user0,mac=00:11:22:33:44:10,path=/tmp/sock0,server=1
> + ,queues=4 -- -i --rxq=4 --txq=4 --rss-ip
>
> -2. Build l3fwd-power sample and launch l3fwd-power with a virtual vhost
> device::
> +2. Build l3fwd-power sample and launch l3fwd-power with a virtual vhost
> device::
>
> - ./l3fwd-power -l 9-12 -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci\
> - --log-level=9 --vdev 'eth_vhost0,iface=/tmp/sock0,queues=4,client=1' -- -p
> 0x1 --parse-ptype 1 \
> + ./l3fwd-power -l 9-12 -n 4 --socket-mem 1024,1024 --legacy-mem --no-pci --
> log-level=9 \
> + --vdev 'eth_vhost0,iface=/tmp/sock0,queues=4,client=1' -- -p 0x1
> + --parse-ptype 1 \
> --config "(0,0,9),(0,1,10),(0,2,11),(0,3,12)"
>
> 3. Send packet by testpmd, check vhost-user multi-cores will keep wakeup
> status::
> diff --git a/test_plans/vhost_event_idx_interrupt_test_plan.rst
> b/test_plans/vhost_event_idx_interrupt_test_plan.rst
> index af75c33..e785755 100644
> --- a/test_plans/vhost_event_idx_interrupt_test_plan.rst
> +++ b/test_plans/vhost_event_idx_interrupt_test_plan.rst
> @@ -77,14 +77,14 @@ Test Case 1: wake up vhost-user core with event idx
> interrupt mode
> --parse-ptype 1 \
> --config "(0,0,1)"
>
> -3. On VM, set ip for virtio device and send packets to vhost by cmds::
> +4. On VM, set ip for virtio device and send packets to vhost by cmds::
>
> ifconfig [ens3] 1.1.1.2
> #[ens3] is the virtual device name
> ping 1.1.1.3
> #send packets to vhost
>
> -4. Check vhost related core is waked up by reading l3fwd-power log.
> +5. Check vhost related core is waked up by reading l3fwd-power log.
>
> Test Case 2: wake up vhost-user cores with event idx interrupt mode 16 queues
> test
> =================================================================
> =================
> @@ -119,12 +119,12 @@ Test Case 2: wake up vhost-user cores with event idx
> interrupt mode 16 queues te
> --parse-ptype 1 \
> --config
> "(0,0,1),(0,1,2),(0,2,3),(0,3,4),(0,4,5),(0,5,6),(0,6,7),(0,7,8),(0,8,9),(0,9,10),(0,10,1
> 1),(0,11,12),(0,12,13),(0,13,14),(0,14,15),(0,15,16)"
>
> -3. Set vitio-net with 16 quques and give vitio-net ip address::
> +4. Set vitio-net with 16 quques and give vitio-net ip address::
>
> ethtool -L [ens3] combined 16 # [ens3] is the name of virtio-net
> ifconfig [ens3] 1.1.1.1
>
> -4. Send packets with different IPs from virtio-net, notice to bind each vcpu to
> different send packets process::
> +5. Send packets with different IPs from virtio-net, notice to bind each vcpu to
> different send packets process::
>
> taskset -c 0 ping 1.1.1.2
> taskset -c 1 ping 1.1.1.3
> @@ -143,11 +143,11 @@ Test Case 2: wake up vhost-user cores with event idx
> interrupt mode 16 queues te
> taskset -c 14 ping 1.1.1.2
> taskset -c 15 ping 1.1.1.2
>
> -5. Check vhost related cores are waked up with l3fwd-power log, such as
> following::
> +6. Check vhost related cores are waked up with l3fwd-power log, such as
> following::
>
> L3FWD_POWER: lcore 0 is waked up from rx interrupt on port 0 queue 0
> - .....
> - .....
> + ...
> + ...
> L3FWD_POWER: lcore 15 is waked up from rx interrupt on port 0 queue 15
>
> Test Case 3: wake up vhost-user cores by multi virtio-net in VMs with event idx
> interrupt mode @@ -193,7 +193,7 @@ Test Case 3: wake up vhost-user cores
> by multi virtio-net in VMs with event idx
> --parse-ptype 1 \
> --config "(0,0,1),(1,0,2)"
>
> -4. On VM1, set ip for virtio device and send packets to vhost::
> +4. On VM1, set ip for virtio device and send packets to vhost::
>
> ifconfig [ens3] 1.1.1.2
> #[ens3] is the virtual device name
> diff --git a/test_plans/vhost_virtio_pmd_interrupt_test_plan.rst
> b/test_plans/vhost_virtio_pmd_interrupt_test_plan.rst
> index b928748..03f4d50 100644
> --- a/test_plans/vhost_virtio_pmd_interrupt_test_plan.rst
> +++ b/test_plans/vhost_virtio_pmd_interrupt_test_plan.rst
> @@ -68,13 +68,13 @@ Test Case 1: Basic virtio interrupt test with 4 queues
>
> 3. Bind virtio port to vfio-pci::
>
> - modprobe vfio enable_unsafe_noiommu_mode=1
> - modprobe vfio-pci
> + modprobe vfio enable_unsafe_noiommu_mode=1
> + modprobe vfio-pci
> ./usertools/dpdk-devbind.py --bind=vfio-pci xx:xx.x
>
> 4. In VM, launch l3fwd-power sample::
>
> - ./l3fwd-power -c 0xf -n 4 --log-level='user1,7' -- -p 1 -P --
> config="(0,0,0),(0,1,1),(0,2,2),(0,3,3)" --no-numa --parse-ptype
> + ./l3fwd-power -c 0xf -n 4 --log-level='user1,7' -- -p 1 -P
> + --config="(0,0,0),(0,1,1),(0,2,2),(0,3,3)" --no-numa --parse-ptype
>
> 5. Send random dest ip address packets to host nic with packet generator,
> packets will distribute to all queues, check l3fwd-power log that all related cores
> are waked up.
>
> @@ -101,7 +101,7 @@ Test Case 2: Basic virtio interrupt test with 16 queues
> -device virtio-net-
> pci,mac=52:54:00:00:00:02,netdev=mynet2,mrg_rxbuf=on,csum=on,mq=on,vec
> tors=40 \
> -vnc :11 -daemonize
>
> -3 Bind virtio port to vfio-pci::
> +3. Bind virtio port to vfio-pci::
>
> modprobe vfio enable_unsafe_noiommu_mode=1
> modprobe vfio-pci
> @@ -109,7 +109,7 @@ Test Case 2: Basic virtio interrupt test with 16 queues
>
> 4. In VM, launch l3fwd-power sample::
>
> - ./l3fwd-power -c 0x0ffff -n 4 --log-level='user1,7' -- -p 1 -P --config
> '(0,0,0),(0,1,1),(0,2,2),(0,3,3)(0,4,4),(0,5,5),(0,6,6),(0,7,7)(0,8,8),(0,9,9),(0,10,10),
> (0,11,11)(0,12,12),(0,13,13),(0,14,14),(0,15,15)' --no-numa --parse-ptype
> + ./l3fwd-power -c 0x0ffff -n 4 --log-level='user1,7' -- -p 1 -P
> + --config
> + '(0,0,0),(0,1,1),(0,2,2),(0,3,3)(0,4,4),(0,5,5),(0,6,6),(0,7,7)(0,8,8)
> + ,(0,9,9),(0,10,10),(0,11,11)(0,12,12),(0,13,13),(0,14,14),(0,15,15)'
> + --no-numa --parse-ptype
>
> 5. Send random dest ip address packets to host nic with packet generator,
> packets will distribute to all queues, check l3fwd-power log that all related cores
> are waked up.
>
> @@ -136,7 +136,7 @@ Test Case 3: Basic virtio-1.0 interrupt test with 4 queues
> -device virtio-net-pci,mac=52:54:00:00:00:02,netdev=mynet2,disable-
> modern=false,mrg_rxbuf=on,csum=on,mq=on,vectors=15 \
> -vnc :11 -daemonize
>
> -3 Bind virtio port to vfio-pci::
> +3. Bind virtio port to vfio-pci::
>
> modprobe vfio enable_unsafe_noiommu_mode=1
> modprobe vfio-pci
> @@ -144,7 +144,7 @@ Test Case 3: Basic virtio-1.0 interrupt test with 4 queues
>
> 4. In VM, launch l3fwd-power sample::
>
> - ./l3fwd-power -c 0xf -n 4 --log-level='user1,7' -- -p 1 -P --
> config="(0,0,0),(0,1,1),(0,2,2),(0,3,3)" --no-numa --parse-ptype
> + ./l3fwd-power -c 0xf -n 4 --log-level='user1,7' -- -p 1 -P
> + --config="(0,0,0),(0,1,1),(0,2,2),(0,3,3)" --no-numa --parse-ptype
>
> 5. Send random dest ip address packets to host nic with packet generator,
> packets will distribute to all queues, check l3fwd-power log that all related cores
> are waked up.
>
> diff --git a/test_plans/virtio_ipsec_cryptodev_func_test_plan.rst
> b/test_plans/virtio_ipsec_cryptodev_func_test_plan.rst
> index 74842ac..47dc332 100644
> --- a/test_plans/virtio_ipsec_cryptodev_func_test_plan.rst
> +++ b/test_plans/virtio_ipsec_cryptodev_func_test_plan.rst
> @@ -30,9 +30,9 @@
> ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
> OF THE POSSIBILITY OF SUCH DAMAGE.
>
> -=======================================
> +========================================
> Cryptodev virtio ipsec Application Tests -
> =======================================
> +========================================
>
>
> Description
> @@ -80,13 +80,15 @@ Prerequisites
> =============
>
> qemu version >= 2.12
> -in qemu enable vhost-user-crypto:
> +in qemu enable vhost-user-crypto::
> +
> ./configure --target-list=x86_64-softmmu --enable-vhost-crypto --
> prefix=/root/qemu-2.12 && make && make install
> +
> the bin is in /root/qemu-2.12 folder, which is your specified
>
> -The options of ipsec-secgw is below:
> +The options of ipsec-secgw is below::
>
> - ./build/ipsec-secgw [EAL options] --
> + ./build/ipsec-secgw [EAL options] --
> -p PORTMASK -P -u PORTMASK -j FRAMESIZE
> -l -w REPLAY_WINOW_SIZE -e -a
> --config (port,queue,lcore)[,(port,queue,lcore]
> @@ -109,28 +111,37 @@ payload in packet by using algorithm setting in VM.
> the packet back to tester.
> Use TCPDump to capture the received packet on tester. Then tester parses the
> payload and compare the payload with correct answer pre-stored in scripts:
>
> - +----------+ +----------------------------------+
> - | | | +--------+ +--------+ |
> - | | -------------|-->| VM0 | -----> | | |
> - | Tester | | +--------+ | VM1 | |
> - | | <------------|-------------------> | | |
> - | | | +--------+ |
> - +----------+ +----------------------------------+
> +.. figure:: image/virtio_ipsec_cryptodev_func_test_plan.png
>
> In Host:
> -# Build DPDK and vhost_crypto app
> - enable CONFIG_RTE_LIBRTE_VHOST in config/common_base
> - make install -j T=x86_64-native-linuxapp-gcc
> - make -C examples/vhost_crypto
> +
> +# Build DPDK and vhost_crypto app::
> +
> + enable CONFIG_RTE_LIBRTE_VHOST in config/common_base
> + make install -j T=x86_64-native-linuxapp-gcc
> + make -C examples/vhost_crypto
>
> # Compile the latest qemu
> -# Run the dpdk vhost sample
> - ./examples/vhost_crypto/build/vhost-crypto --socket-mem 2048,0 --legacy-
> mem -w 1a:01.0 -w 1c:01.0 -w 1e:01.0 --vdev
> crypto_scheduler_pmd_1,slave=0000:1a:01.0_qat_sym,slave=0000:1c:01.0_qat
> _sym,slave=0000:1e:01.0_qat_sym,mode=round-robin,ordering=enable -l
> 8,9,10,11,12 -n 6 -- --config "(9,0,0),(10,0,0),(11,0,0),(12,0,0)" --socket-file
> 9,/tmp/vm0_crypto0.sock --socket-file=10,/tmp/vm0_crypto1.sock --socket-
> file=11,/tmp/vm1_crypto0.sock --socket-file=12,/tmp/vm1_crypto1.sock
>
> -# bind vfio-pci
> +# Run the dpdk vhost sample::
> +
> + ./examples/vhost_crypto/build/vhost-crypto \
> + --socket-mem 2048,0 --legacy-mem \
> + -w 1a:01.0 -w 1c:01.0 -w 1e:01.0 \
> + --vdev
> crypto_scheduler_pmd_1,slave=0000:1a:01.0_qat_sym,slave=0000:1c:01.0_qat
> _sym,slave=0000:1e:01.0_qat_sym,mode=round-robin,ordering=enable \
> + -l 8,9,10,11,12 -n 6 \
> + -- --config "(9,0,0),(10,0,0),(11,0,0),(12,0,0)" \
> + --socket-file 9,/tmp/vm0_crypto0.sock \
> + --socket-file=10,/tmp/vm0_crypto1.sock \
> + --socket-file=11,/tmp/vm1_crypto0.sock \
> + --socket-file=12,/tmp/vm1_crypto1.sock
> +
> +# bind vfio-pci::
> +
> usertools/dpdk-devbind.py --bind=vfio-pci 0000:60:00.0 0000:60:00.1
> 0000:3b:00.0 0000:3b:00.1
>
> -# Start VM0 by the qemu
> +# Start VM0 by the qemu::
> +
> taskset -c 11,12,13,14 /root/qemu-2/bin/qemu-system-x86_64 -name vm0 -
> enable-kvm -pidfile /tmp/.vm0.pid
> -daemonize -monitor unix:/tmp/vm0_monitor.sock,server,nowait
> -net nic,vlan=0,macaddr=00:00:00:42:65:aa,model=e1000,addr=1f -net
> user,vlan=0,hostfwd=tcp:10.67.111.126:6000-:22
> @@ -143,7 +154,8 @@ In Host:
> -device vfio-pci,host=0000:3b:00.0,id=pt_0
> -device vfio-pci,host=0000:3b:00.1,id=pt_1
>
> -# Start VM1 by the qemu
> +# Start VM1 by the qemu::
> +
> taskset -c 15,16,17,18 /root/qemu-2/bin/qemu-system-x86_64 -name vm1 -
> enable-kvm -pidfile /tmp/.vm1.pid
> -daemonize -monitor unix:/tmp/vm1_monitor.sock,server,nowait
> -net nic,vlan=0,macaddr=00:00:00:db:2e:f9,model=e1000,addr=1f -net
> user,vlan=0,hostfwd=tcp:10.67.111.126:6001-:22
> @@ -157,7 +169,9 @@ In Host:
> -device vfio-pci,host=0000:60:00.1,id=pt_1
>
> In VM
> -# set virtio device
> +
> +# set virtio device::
> +
> modprobe uio_pci_generic
> echo -n 0000:00:04.0 > /sys/bus/pci/drivers/virtio-pci/unbind
> echo -n 0000:00:05.0 > /sys/bus/pci/drivers/virtio-pci/unbind
> @@ -166,13 +180,19 @@ In VM
> # Run the ipsec test cases cmd
>
> 1. AESNI_MB case Command line Eg:
> - In vm0:
> + In vm0::
> +
> ./examples/ipsec-secgw/build/ipsec-secgw --socket-mem 1024,0 -w
> 0000:00:06.0 -w 0000:00:07.0 --vdev crypto_aesni_mb_pmd_1 --vdev
> crypto_aesni_mb_pmd_2 -l 1,2,3 -n 4 -- -P --config "(0,0,2),(1,0,3)" -u 0x1 -p
> 0x3 -f /root/ipsec_test0.cfg
> - In vm1:
> +
> + In vm1::
> +
> ./examples/ipsec-secgw/build/ipsec-secgw --socket-mem 1024,0 -w
> 0000:00:06.0 -w 0000:00:07.0 --vdev crypto_aesni_mb_pmd_1 --vdev
> crypto_aesni_mb_pmd_2 -l 1,2,3 -n 4 -- -P --config "(0,0,2),(1,0,3)" -u 0x1 -p
> 0x3 -f /root/ipsec_test1.cfg
>
> 2. VIRTIO case Command line Eg:
> - In vm0:
> + In vm0::
> +
> ./examples/ipsec-secgw/build/ipsec-secgw --socket-mem 1024,0 -w
> 0000:00:06.0 -w 0000:00:07.0 -w 00:04.0 -w 00:05.0 -l 1,2,3 -n 4 -- -P --config
> "(0,0,2),(1,0,3)" -u 0x1 -p 0x3 -f /root/ipsec_test0.cfg
> - In vm1:
> +
> + In vm1::
> +
> ./examples/ipsec-secgw/build/ipsec-secgw --socket-mem 1024,0 -w
> 0000:00:06.0 -w 0000:00:07.0 -w 00:04.0 -w 00:05.0 -l 1,2,3 -n 4 -- -P --config
> "(0,0,2),(1,0,3)" -u 0x1 -p 0x3 -f /root/ipsec_test1.cfg diff --git
> a/test_plans/virtio_perf_cryptodev_func_test_plan.rst
> b/test_plans/virtio_perf_cryptodev_func_test_plan.rst
> index 74d38f6..3ad6543 100644
> --- a/test_plans/virtio_perf_cryptodev_func_test_plan.rst
> +++ b/test_plans/virtio_perf_cryptodev_func_test_plan.rst
> @@ -30,9 +30,9 @@
> ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
> OF THE POSSIBILITY OF SUCH DAMAGE.
>
> -=======================================
> +==============================================
> Cryptodev virtio Performance Application Tests -
> =======================================
> +==============================================
>
>
> Description
> @@ -55,7 +55,7 @@ Part of the algorithms are not supported currently.
> +-----------+-------------------+--------------------------------------------------------------
> -------------+
> | sha | | sha1, sha2-224, sha2-384, sha2-256, sha2-512
> |
> +-----------+-------------------+--------------------------------------------------------------
> -------------+
> -| hmac | | Support sha implementations sha1, sha2-224, sha2-256,
> |
> +| hmac | | Support sha implementations sha1, sha2-224, sha2-256,
> |
> | | | |
> | | | sha2-384, sha2-512 |
> +-----------+-------------------+--------------------------------------------------------------
> -------------+
> @@ -71,7 +71,7 @@ Part of the algorithms are not supported currently.
> +-----------+-------------------+--------------------------------------------------------------
> -------------+
> | sha | | sha1, sha2-224, sha2-384, sha2-256, sha2-512
> |
> +-----------+-------------------+--------------------------------------------------------------
> -------------+
> -| hmac | | Support sha implementations sha1, sha2-224, sha2-256,
> |
> +| hmac | | Support sha implementations sha1, sha2-224, sha2-256,
> |
> | | | |
> | | | sha2-384, sha2-512 |
> +-----------+-------------------+--------------------------------------------------------------
> -------------+
> @@ -81,8 +81,10 @@ Prerequisites
> =============
>
> qemu version >= 2.12
> -in qemu enable vhost-user-crypto:
> +in qemu enable vhost-user-crypto::
> +
> ./configure --target-list=x86_64-softmmu --enable-vhost-crypto --
> prefix=/root/qemu-2.12 && make && make install
> +
> the bin is in /root/qemu-2.12 folder, which is your specified
>
> Test case setup:
> @@ -97,19 +99,24 @@ Test case setup:
> +--------------+
>
> In Host:
> -# Build DPDK and vhost_crypto app
> +
> +# Build DPDK and vhost_crypto app::
> +
> enable CONFIG_RTE_LIBRTE_VHOST in config/common_base
> make install -j T=x86_64-native-linuxapp-gcc
> make -C examples/vhost_crypto
>
> # Compile the latest qemu
> -# Run the dpdk vhost sample
> +# Run the dpdk vhost sample::
> +
> ./examples/vhost_crypto/build/vhost-crypto --socket-mem 2048,0 --legacy-
> mem --vdev crypto_aesni_mb_pmd_1 -l 8,9,10 -n 4 -- --config "(9,0,0),(10,0,0)"
> --socket-file 9,/tmp/vm0_crypto0.sock --socket-file=10,/tmp/vm0_crypto1.sock
>
> -# bind vfio-pci
> +# bind vfio-pci::
> +
> usertools/dpdk-devbind.py --bind=vfio-pci 0000:60:00.0 0000:60:00.1
>
> -# Start VM by the qemu
> +# Start VM by the qemu::
> +
> taskset -c 11,12,13,14 /root/qemu-2/bin/qemu-system-x86_64 -name vm0
> -enable-kvm -pidfile /tmp/.vm0.pid
> -cpu host -smp 4
> @@ -127,7 +134,9 @@ In Host:
> -device vfio-pci,host=0000:60:00.1,id=pt_1
>
> In VM:
> -# set virtio device
> +
> +# set virtio device::
> +
> modprobe uio_pci_generic
> echo -n 0000:00:04.0 > /sys/bus/pci/drivers/virtio-pci/unbind
> echo -n 0000:00:05.0 > /sys/bus/pci/drivers/virtio-pci/unbind
> @@ -135,10 +144,17 @@ In VM:
>
> # Run the virtio performance test cases
>
> - 1. The AESNI_MB case Command line Eg:
> + 1. The AESNI_MB case Command line Eg::
>
> - ./build/app/dpdk-test-crypto-perf -c 0xf --vdev crypto_aesni_mb_pmd -- --
> ptest throughput --devtype crypto_aesni_mb --optype cipher-then-auth --
> cipher-algo aes-cbc --cipher-op encrypt --cipher-key-sz 16 --cipher-iv-sz 16 --
> auth-algo sha1-hmac --auth-op generate --auth-key-sz 64 --auth-aad-sz 0 --
> auth-digest-sz 20 --total-ops 10000000 --burst-sz 32 --buffer-sz 1024
> + ./build/app/dpdk-test-crypto-perf -c 0xf --vdev crypto_aesni_mb_pmd \
> + -- --ptest throughput --devtype crypto_aesni_mb --optype cipher-then-auth
> \
> + --cipher-algo aes-cbc --cipher-op encrypt --cipher-key-sz 16 --cipher-iv-sz 16
> \
> + --auth-algo sha1-hmac --auth-op generate --auth-key-sz 64 --auth-aad-sz 0
> \
> + --auth-digest-sz 20 --total-ops 10000000 --burst-sz 32
> + --buffer-sz 1024
>
> - 2. The VIRTIO case Command line Eg:
> + 2. The VIRTIO case Command line Eg::
>
> - ./build/app/dpdk-test-crypto-perf -c 0xf -w 00:05.0 -- --ptest throughput --
> devtype crypto_qat --optype cipher-then-auth --cipher-algo aes-cbc --cipher-op
> encrypt --cipher-key-sz 16 --cipher-iv-sz 16 --auth-algo sha1-hmac --auth-op
> generate --auth-key-sz 64 --auth-aad-sz 0 --auth-digest-sz 20 --total-ops
> 10000000 --burst-sz 32 --buffer-sz 1024
> + ./build/app/dpdk-test-crypto-perf -c 0xf -w 00:05.0 -- --ptest throughput \
> + --devtype crypto_qat --optype cipher-then-auth --cipher-algo aes-cbc --
> cipher-op encrypt \
> + --cipher-key-sz 16 --cipher-iv-sz 16 --auth-algo sha1-hmac --auth-op
> generate --auth-key-sz 64 \
> + --auth-aad-sz 0 --auth-digest-sz 20 --total-ops 10000000
> + --burst-sz 32 --buffer-sz 1024
> --
> 1.8.3.1
next prev parent reply other threads:[~2019-04-30 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 7:46 [dts] [PATCH V1 1/3] test_plans/virtio_ipsec_cryptodev_func: use a PNG file to show the topology Wenjie Li
2019-04-30 7:46 ` [dts] [PATCH V1 2/3] test_plans: fix build error/warning Wenjie Li
2019-04-30 7:47 ` Li, WenjieX A [this message]
2019-04-30 7:46 ` [dts] [PATCH V1 3/3] test_plans/index: fix build warning Wenjie Li
2019-04-30 7:47 ` Li, WenjieX A
2019-04-30 7:47 ` [dts] [PATCH V1 1/3] test_plans/virtio_ipsec_cryptodev_func: use a PNG file to show the topology Li, WenjieX A
2019-05-13 7:46 ` Tu, Lijuan
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=8688172CD5C0B74590FAE19D9579F94B536DDC3C@SHSMSX103.ccr.corp.intel.com \
--to=wenjiex.a.li@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).