DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 682] [dpdk-21.05]metering_and_policing: Invalid group ID: Invalid argument
Date: Wed, 21 Apr 2021 06:06:01 +0000	[thread overview]
Message-ID: <bug-682-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=682

            Bug ID: 682
           Summary: [dpdk-21.05]metering_and_policing: Invalid group ID:
                    Invalid argument
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: longfengx.liang@intel.com
  Target Milestone: ---

Environment


DPDK version: Use make showversion or for a non-released version: git remote -v
&& git show-ref --heads
21.05.0-rc0:1cd3ce09534e035b3b3cfe0475adee656971fd8c
Other software versions: name/version for QEMU, OVS, etc. Repeat as required.
OS: Fedora 33 5.9.10-200.fc33.x86_64
Compiler: gcc (GCC) 10.2.1 20201016 (Red Hat 10.2.1-6)
Hardware platform: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
NIC hardware: XL710 for 40GbE QSFP+
Driver version: 2.15.9
NIC firmware: 8.30 0x8000a4ae 1.2926.0

Test Setup
Steps to reproduce
List the steps to reproduce the issue.

1. build dpdk 
# rm -rf x86_64-native-linuxapp-gcc
# CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib
-Dc_args='-DRTE_EAL_IGB_UIO=1' --default-library=static
x86_64-native-linuxapp-gcc 
# ninja -C x86_64-native-linuxapp-gcc -j 70 


2. tester preparation
# scp -v .dts/dep/meter_and_policy_config.tar.gz root@10.240.183.141:/tmp

3. DUT preparation
# ./usertools/dpdk-devbind.py -b vfio-pci 0000:84:00.0 0000:84:00.1
# tar xf /tmp/meter_and_policy_config.tar.gz -C /root/dpdk/drivers/net/softnic 
# cp /root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli
/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-5 
# sed -i -e 's/^.*link LINK0 dev.*$/link LINK0 dev 0000:84:00.0/g'
/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-5 
# sed -i -e 's/^.*link LINK1 dev.*$/link LINK1 dev 0000:84:00.1/g'
/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-5 
# sed -i -e 's/^.*table action profile AP0.*$/table action profile AP0 ipv4
offset 270 fwd meter trtcm tc 1 stats pkts/g'
/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-5 
# sed -i -e 's/^.*pipeline RX table match.*$/pipeline RX table match acl ipv4
offset 270 size 4K action AP0/g'
/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-5 
# sed -i -e 's/thread 5 pipeline RX enable/thread 2 pipeline RX enable/g'
/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-5 
# sed -i -e 's/thread 5 pipeline TX enable/thread 2 pipeline TX enable/g'
/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-5

4. lanch app 
# x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 0,1,2 -n 4 -a 0000:84:00.0 -a
0000:84:00.1 --file-prefix=dpdk_18582_20210418103702  -s 0x4 --vdev
'net_softnic0,firmware=/root/dpdk/drivers/net/softnic/meter_and_policing_firmware.cli-5'
-- -i --rxq=2 --txq=2 --portmask=0x4 --disable-rss
# add port meter profile trtcm_rfc2698 2 0 3125000000 3125000000 400 500
# create port meter 2 0 0 yes d d d 0 0 0
# flow create 2 group 0 ingress pattern eth / ipv4 proto mask 255 src mask
255.255.255.255 dst mask 255.255.255.255 src spec 1.10.11.12 dst spec
2.20.21.22 proto spec 6 / tcp src mask 65535 dst mask 65535 src spec 2 dst spec
2 / end actions meter mtr_id 0 / queue index 0 / end
Show the output from the previous commands.

# testpmd> add port meter profile trtcm_rfc2698 2 0 3125000000 3125000000 400
500
Bad arguments
# testpmd> create port meter 2 0 0 yes d d d 0 0 0
meter profile id: Meter profile id not valid (error 2)
# testpmd> flow create 2 group 0 ingress pattern eth / ipv4 proto mask 255 src
mask 255.255.255.255 dst mask 255.255.255.255 src spec 1.10.11.12 dst spec
2.20.21.22 proto spec 6 / tcp src mask 65535 dst mask 65535 src spec 2 dst spec
2 / end actions meter mtr_id 0 / queue index 0 / end
port_flow_complain(): Caught PMD error type 3 (group field): cause:
0x7ffe0125f3c8, Invalid group ID: Invalid argument
# testpmd> EAL: Error reading from file descriptor 23: Input/output error
EAL: Error reading from file descriptor 26: Input/output error
Killed
Expected Result
Explain what is the expected result in text or as an example output:

# testpmd> add port meter profile trtcm_rfc2698 2 0 3125000000 3125000000 400
500
# testpmd> create port meter 2 0 0 yes d d d 0 0 0
# testpmd> flow create 2 group 0 ingress pattern eth / ipv4 proto mask 255 src
mask 255.255.255.255 dst mask 255.255.255.255 src spec 1.10.11.12 dst spec
2.20.21.22 proto spec 6 / tcp src mask 65535 dst mask 65535 src spec 2 dst spec
2 / end actions meter mtr_id 0 / queue index 0 / end
Flow rule #0 created

Regression
Is this issue a regression: (Y/N) Y

[root@localhost dpdk]# git show c5a3860f36902e1701817b0961bf99a5c96ede3a
commit c5a3860f36902e1701817b0961bf99a5c96ede3a (HEAD)
Author: Li Zhang <lizh@nvidia.com>
Date: Tue Apr 13 18:59:55 2021 +0300

app/testpmd: add meter profile packet mode option

add meter profile packet_mode to the ethernet device.
One example:
add port meter profile rfc2697 (port_id) (profile_id)
(cir) (cbs) (ebs) (packet_mode)

Signed-off-by: Li Zhang <lizh@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>
Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>

Stack Trace or Log

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2021-04-21  6:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21  6:06 bugzilla [this message]
2021-04-21  6:51 ` bugzilla

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=bug-682-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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).