[dpdk-dev] [Bug 449] Fortville X710 FDIR with flow APIs broken

[dpdk-dev] [Bug 449] Fortville X710 FDIR with flow APIs broken

[bugzilla]

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

            Bug ID: 449
           Summary: Fortville X710 FDIR with flow APIs broken
           Product: DPDK
           Version: 20.02
          Hardware: x86
               URL: https://doc.dpdk.org/dts/test_plans/generic_flow_api_t
                    est_plan.html
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: eventdev
          Assignee: dev@dpdk.org
          Reporter: vipin.varghese@intel.com
  Target Milestone: ---

DPDK version tested: 19.11.1 & 20.2

section: 28.5, Flow config for VF-0 for ipv4-other

Rule: 

1. `flow create 0 ingress pattern eth / ipv4 src is 192.168.0.1 dst is
192.168.0.2 proto is 3 / vf id is 0 / end actions queue index 1 / end`
2. `flow create 0 ingress pattern eth / ipv4 src is 11.11.11.11 dst is
12.12.12.12 proto is 17 / vf id is 0 / end actions queue index 1 / end`
3. `flow create 0 ingress pattern eth / ipv4 proto is 17 / vf id is 0 / end
actions queue index 1 / end`

Result: `Caught error type 13 (specific pattern item): cause: 0x17ff5b140,
Matching VF traffic without affecting it (transfer attribute) is unsupported:
Operation not supported`

CMD:
a. PF: ``` ./x86_64-native-linuxapp-gcc/app/testpmd -l 14-15 -w 08:00.0
--socket-mem=128  -- -i --rxq=4 --txq=4 --disable-rss
--pkt-filter-mode=perfect```
b. VF: ```./x86_64-native-linuxapp-gcc/app/testpmd -l 16-17 -w 0000:08:02.0
--socket-mem=128,0  --file-prefix=vf  -- -i --rxq=4 --txq=4 --disable-rss
--pkt-filter-mode=perfect```

on both: 
```
set fwd rxonly
set verbose 1
start
```

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

[dpdk-dev] [Bug 449] Fortville X710 FDIR with flow APIs broken

[bugzilla]

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

Steve Yang (stevex.yang@intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stevex.yang@intel.com
         Resolution|---                         |INVALID
             Status|CONFIRMED                   |RESOLVED

--- Comment #13 from Steve Yang (stevex.yang@intel.com) ---
Not a bug.

Correct use steps：
1. bind the pf to dpdk driver::
    ./usertools/dpdk-devbind.py -b igb_uio 1b:00.0

2. add one vf on dpdk pf, then bind the vf to vfio-pci::
  echo 1 >/sys/bus/pci/devices/0000:1b:00.0/max_vfs
   ./usertools/dpdk-devbind.py -b igb_uio 1b:02.0

3. launch the app ``testpmd`` with the following arguments::
   ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -w 1b:00.0
--file-prefix=pf – -i --rxq=4 --txq=4

    testpmd> set verbose 1
    testpmd> start


    ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 -w 1b:02.0
--file-prefix=vf – -i --rxq=4 --txq=4

     testpmd> set verbose 1
     testpmd> start

4. create filter rule and sent pkg::
flow create 0 ingress transfer  pattern eth / ipv4 src is 11.11.11.11 dst is
12.12.12.12 proto is 255 / vf id is 0 / end actions queue index 1 / end

sendp([Ether(dst='3C:FD:FE:DC:F1:88')/IP(src='11.11.11.11',dst='12.12.12.12',proto=255)/("X"*480)],
iface="enp27s0f1", count=1)

5. flow create 0 ingress transfer  pattern eth / ipv4 src is 11.11.11.11 dst is
12.12.12.12 / udp / vf id is 0 / end actions queue index 1 / end

sendp([Ether(dst='3C:FD:FE:DC:F1:88')/IP(src='11.11.11.11',dst='12.12.12.12',proto=17)/("X"*480)],iface="enp27s0f1",
count=1)


Note:
① dst mac is a random mac address, not a pf mac
② proto is 17 means UDP, so create the following rule  and send the packet with
proto is 17 cannot matched。

flow create 0 ingress transfer  pattern eth / ipv4 src is 11.11.11.11 dst is
12.12.12.12 proto is 17 / vf id is 0 / end actions queue index 1 / end

sendp([Ether(dst='3C:FD:FE:DC:F1:88')/IP(src='11.11.11.11',dst='12.12.12.12',proto=17)/("X"*480)],
iface="enp27s0f1", count=1)

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

[dpdk-dev] [Bug 449] Fortville X710 FDIR with flow APIs broken

[bugzilla]

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

Vipin Varghese (vipin.varghese@intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|INVALID                     |---
             Status|RESOLVED                    |CONFIRMED

--- Comment #14 from Vipin Varghese (vipin.varghese@intel.com) ---
Marking this as fixed `confirmed` rather than `resolved-invalid` due to the
following reasons

1. ticket is opened on DPDK 20.02 on 13 Apr 2020
2. The documentation available for FDIR on X710 was not correct
3. missing of `transfer` verb in the documentation of testpmd and tests.
4. Patches and fixes applied on top of X710 before testing on 30 Dec 2020.
5. Not mentioned in the comment whether it works for `DPDK 20.02`
6. Have not confirmed if the VF can be used with any other application other
than testpmd.

@Ajith will test and try on DPDK 20.02 but with much lower priority to confirm
with the steps shared from `Steve Yang` and update the ticket.

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