vipinpv85 / dpdk_suricata-4_1_1 Goto Github PK

dpdk infrastructure for software acceleration. Currently working on RX and ACL pre-filter

License: MIT License

Makefile 2.78% Shell 3.71% M4 0.84% Perl 0.25% Python 1.60% C 80.19% CSS 0.01% Roff 0.05% PHP 0.04% C++ 6.78% Lua 0.01% Rust 3.66% Dockerfile 0.01% SmPL 0.04% Raku 0.05%

dpdk suricata acl offloading

dpdk_suricata-4_1_1's Introduction

DPDK_SURICATA-4_1_4

porting ACL from 3.0 - on hold creating patch request for dev branch of Suricata 6.0

Motivation

Create simple DPDK RX-TX to allow packets into SURICATA processing pipeiline mode.

Things to do

flatten the packet buffer for full zero-copy mode.
use zero copy PKT decode and other layers

Work in progress

use SW ACL for classification on directional rules from https://github.com/vipinpv85/DPDK-Suricata_3.0.

Things completed

How to Build?

dependency

https://suricata.readthedocs.io/en/suricata-4.1.2/install.html

version:

software	release
DPDK	dpdk-stable-19.11.3
Suricata	suricata-4.1.4

Build and Run

DPDK 19.11.3

Download DPDK from dpdk.org.
Untar DPDK tar file.
Execute the following commands

 cd <to unatar dpdk folder>
 make config T=x86_64-native-linuxapp-gcc O=x86_64-native-linuxapp-gcc
 export RTE_SDK=$PWD
 export RTE_TARGET=x86_64-native-linuxapp-gcc
 cd x86_64-native-linuxapp-gcc
 make -j 4

Test the custom build by cross checking examples like helloworld & l2fwd.

modified suricata:

steps	explanation
`autoconf`	to build the configure script with DPDK support
`./configure --enable-dpdk`	makes configuration with dpdk
`make -j 10`	build suricata with 10 threads

How to Run?

command	purpose
`./src/suricata --build-info; ./src/suricata --list-runmodes`	get suricata version and supported modes
`./src/suricata --list-dpdkports`	list DPDK available ports
`./src/suricata --dpdk`	Run DPDK suircata

How to run on multiple NUMA sockets

DPDK API makes use of Huge pages
Pin the memory to per NUMA by editing EAL args
Pin the worker threads by eiditing affinity in suricata.yaml

edit suricata.yaml
Search for dpdk
under EAL append options '--socket-mem=1,1024' and '--scoket-limit=1,1024' for NUMA-1
under cpu-affinity update worker-cpu-set for desired NUMA-1 threads

Work item in discussion with SURICATA team to merge

Introduction:
1. DPDK is set of Hardware and Software library, that helps to run on userspace.
2. DPDK process is classified as Primary & Secondary, where huge pages and devices are shared between them.
3. For an existing application to be support DPDK; both build and code is to be changed.
4. One can skip the DPDK lcore-threads and service-threads too. But has to invoke `rte_eal_init` and relevant library call.

What mode to use: (to be decided - which one to support and start)

1. Primary (singleton/monolithic):

Pros:
a) Suricata will run as Primary managing all DPDK PMD and Libraries.
b) Requires access to hugepages and root permission.
c) Does not need ASLR to be disabled.
d) can run in baremetal CPU, VM, Docker too.
e) can make use DPDK secondary apps like proc-info, pdump, any other custom secondary application.
Cons:
a) pausible to run as non root, but requires DPDK familirity.
b) code becomes bulky.
c) HW vendor or device offload, code needs to updated with generic API or SW fallback.

2. Seocndary:

Pros:
a) Suricata will run as Secondary with zero or a little managment and setup code for PMD and Libraries.
b) Requires access to hugepages and root permission.
c) ASLR needs to be disabled, for consistent or hiigher chance of start.
d) can run in baremetal CPU, VM, Docker too.
e) Code becomes lighter.
Cons:
a) plausible to run as non-root, but requires DPDK familiarity.
b) cannot make use of DPDK secondary apps like proc-info, pdump, any other custom secondary application.
c) Need to probe the configuration settings for HW vendor or device offload.

3. Detached Primary:

Pros:
a) Suricata will run as Primary, getting packets from another DPDK primary via memif/vhost/AF_XDP interface.
b) Requires access to huge pages and root permission.
c) can run in bare-metal CPU, VM, Docker too.
d) Code becomes lighter because we are using SW generic NIC and offloads.
e) all vendor-specific and non DPDK offloads can be run on the alternative process.
f) Useful in scenarios where selected packet mirror can be implemented in HW, or SW and fed to DPDK.
g)
Cons:
a) plausible to run as non-root, but requires DPDK familiarity.
b) secondary apps like proc-info, pdump, any other custom secondary application works.
c) can make use of XDP (eBPF) to redirect selected traffic too.

How to do:
1. There are ABI and API changes across DPDK releases.
2. Use a long term stable release as de-facto for DPDK. example 19.11.1 LTS.
3. Depending upon individual or distro releases not all NIC, HW or features are enabled.
4. Identify and choose the most common NIC like memif/Pcap/tap/vhost for ease of build.
5. Update `configure.ac` to reflect
a) $RTE_SDK & $RTE_TARGET for custom or distro dpdk package.
b) edit for new field `--enable-dpdk` as flag
c) add necessary changes for CFLAGS and LDFLAGS if flag is enabled.
6. Add Compiler flag `HAVE_DPDK` to build for DPDK mode.
7. Start for single and multi worker mode.
8. Code changes in
a) suricata.c: for DPDK initialization, run-mode registration, parse of suricata.yaml for DPDK sections and add-hook to Rules Add for DPDK ACL.
b) source-dpdk, run mode-dpdk: new files to support DPDK configuration and worker threads.

Proof of concept with single worker mode: https://github.com/vipinpv85/DPDK-Suricata_3.0
ongoing work with multi-worker: https://github.com/vipinpv85/DPDK_SURICATA-4_1_1

Performance: by redirecting rule match packets to worker threads
1. 1 worker can perform around 1.25 Mpps
2. 10Gbps with line rate (64byte) we need to 14 workers with each worker having 1Mpps flows
3. 40Gbps with line rate (128byte) we need 30 worker threads with 1Mpps flows each.

dpdk_suricata-4_1_1's People

Contributors

Stargazers

Watchers

Forkers

benhe119 netpass trafgen decanio wlm328cs csqjxiao johnny5188 tritm shield-liu parker1014 wang-xuefei runtest007 wyao51 fy45 kofee ziqi521 bjdudu lzskyline coder-gao xifeng6 grehxscape looking-for-vest helloerror92 dreamflychen taskiller anrongwn chong6qing a412160060 liujianqun zhaoruixbj jkmaple zhoyo21th hackerdao ritel126 jianyongchen himetre clockdad xizhimen evilares witwait arryboom mikeswer l1l1ng

dpdk_suricata-4_1_1's Issues

vmware vmxnet3 [ERRCODE: SC_ERR_DPDK_CONFIG(319)] - Failed to configure port [0]

[root@localhost bin]# ./suricata --dpdk
28/6/2021 -- 17:29:45 - - DPDK Mode selected
28/6/2021 -- 17:29:45 - - (name:suricatareassembly)
28/6/2021 -- 17:29:45 - - (n:8000)
28/6/2021 -- 17:29:45 - - This is Suricata version 4.1.4 RELEASE
28/6/2021 -- 17:29:46 - - [ERRCODE: SC_ERR_NO_RULES(42)] - No rule files match the pattern /usr/local/var/lib/suricata/rules/suricata.rules
28/6/2021 -- 17:29:46 - - [ERRCODE: SC_ERR_NO_RULES_LOADED(43)] - 1 rule files specified, but no rule was loaded at all!
28/6/2021 -- 17:29:46 - - Port 0 RX-q (4) hence trying RSS
Ethdev port_id=0 requested Rx offloads 0xe doesn't match Rx offloads capabilities 0x82a1d in rte_eth_dev_configure()
28/6/2021 -- 17:29:46 - - [ERRCODE: SC_ERR_DPDK_CONFIG(319)] - Failed to configure port [0]
28/6/2021 -- 17:29:46 - - [ERRCODE: SC_ERR_DPDK_CONFIG(319)] - Failed to setup Ports!
28/6/2021 -- 17:29:46 - - [ERRCODE: SC_ERR_DPDK_CONFIG(319)] - Failed to set config!

Clarification?

Hi,

I was not able to understand what does PKT emptyrx in the stats mean?

Can describe as IDS or IPS,how to build the network topology?

Can describe as IDS or IPS, in the two scenarios, how to build the network topology? Can you give me an example? Thanks a lot.
This may help more people understand how to use ids and ips. It is best to solve the network problem with a computer

vmware centos7 e1000 Failed to configure port [0]

hello,firstly,i have added -Wl,-lrte_pmd_e1000 in configure.ac , and i set queues=1 in yaml(because e1000 can't support rss),then i run it,it will "Ethdev port_id=0 nb_tx_queues=2 > 1" , so i set txq_count=1 , then :Ethdev port_id=0 invalid rss_hf: 0x3bffc, valid value: 0x0

and l2fwd can work normally

i didn't know why caused it? can you help me? thank you !

Issue getting Suricata to listen on DPDK ports

Hello Vipin,
Was hoping you could help me with this. I setup DPDK Suricata according to your instructions but having issues getting Suricata to listen on DPDK ports. This is the issue I am getting:

When I run --list-dpdkports, this is the output I am getting, it appears that this is the port is being found.

This is the result of running DPDK-devbind to view existing ports.

I believe that there is something wrong in my config file. This is a snapshot of my yaml file, specifically the DPDK portion.

Please let me know if there is something obvious I am doing wrong, or if you would be available for a live debug over zoom.

Thanks

Suricata as a lib

Hello,
I am wondering why do we use suricata as a lib in DPDK instead of DPDK as a lib of suricata.

If so we can easy to handle suricata

[ERRCODE: SC_ERR_DPDK_CONFIG(319)] - Failed to setup Ports!

suricata --dpdk

20/3/2022 -- 19:20:18 - - addr_dst_match4_cnt 1 addr_src_match4_cnt 1 addr_dst_match6_cnt i1 addr_src_match6_cnt 1
20/3/2022 -- 19:20:18 - - IPV4
20/3/2022 -- 19:20:18 - - 0:ffffffff
20/3/2022 -- 19:20:18 - - 0:ffffffff
20/3/2022 -- 19:20:18 - - -----------------------
20/3/2022 -- 19:20:18 - - IPV6
20/3/2022 -- 19:20:18 - - 0-0-0-0:ffffffff-ffffffff-ffffffff-ffffffff
20/3/2022 -- 19:20:18 - - 0-0-0-0:ffffffff-ffffffff-ffffffff-ffffffff
20/3/2022 -- 19:20:18 - - -----------------------
20/3/2022 -- 19:20:18 - - Source Port
20/3/2022 -- 19:20:18 - - port:port2 (0:ffff)
20/3/2022 -- 19:20:18 - - Destiantion Port
20/3/2022 -- 19:20:18 - - port:port2 (0:ffff)
20/3/2022 -- 19:20:18 - - prio 3
20/3/2022 -- 19:20:18 - - Port 0 RX-q (4) hence trying RSS
20/3/2022 -- 19:20:18 - - [ERRCODE: SC_ERR_DPDK_CONFIG(319)] - Failed to setup Ports!
20/3/2022 -- 19:20:18 - - [ERRCODE: SC_ERR_DPDK_CONFIG(319)] - Failed to set config!

DPDK:

./build/app/testpmd -l 0-1 -n 2 -- -i
EAL: Detected 2 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:02:01.0 on NUMA socket -1
EAL: probe driver: 8086:100f net_e1000_em
EAL: PCI device 0000:02:05.0 on NUMA socket -1
EAL: probe driver: 8086:100f net_e1000_em
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL: probe driver: 8086:10d3 net_e1000_em
Interactive-mode selected
testpmd: create a new mbuf pool <mbuf_pool_socket_0>: n=155456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
Configuring Port 0 (socket 0)
Port 0: 00:0C:29:CE:9F:CF
Configuring Port 1 (socket 0)
Port 1: 00:0C:29:CE:9F:D9
Checking link statuses...

dpdk-stable-19.11.11 and Suricata version 4.1.4 RELEASE;

So I want to know how to solve this problem？Thank you for your replay.

Suricata start failed: No DPDK ports found

suricata --dpdk

19/8/2020 -- 16:01:30 - - DPDK Mode selected
19/8/2020 -- 16:01:30 - - (name:suricatareassembly)
19/8/2020 -- 16:01:30 - - (n:8000)
19/8/2020 -- 16:01:30 - - This is Suricata version 4.1.4 (rev 09ee165)
19/8/2020 -- 16:01:30 - - [ERRCODE: SC_ERR_DPDK_CONFIG(319)] - No DPDK ports found

There are different from:
#5

I can't find the "mysuricata.cfg" file, I don't even know what format to input into this file.

I found the DPDK options in the "suricate.yml" file, I guess it's a update, but how can I set it?

what is the difference between DPDK_SURICATA-4_1_1 and DPDK-Suricata_3.0?

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

I have some questions about "Work item in discussion with SURICATA team to merge" in README.md

You said that you didn't decide which mode to use. Have all three modes not been implemented in DPDK_SURICATA-4_1_1?But i learn your open source and i think you has been implemented the frist mode(Primary (singleton/monolithic)).

thanks!

[Help] Error when trying to build suricata 5.0.0 and dpdk 18.11.2

Hello @vipinpv85,
I have tried to build suricata 5.0.0 with dpdk 18.11.2 and I got an error:

dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h:134:2: error: expected specifier-qualifier-list before ‘STAILQ_ENTRY’
  STAILQ_ENTRY(rte_mempool_objhdr) next; /**< Next in list. */
  ^
dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h:149:1: warning: data definition has no type or storage class [enabled by default]
 STAILQ_HEAD(rte_mempool_objhdr_list, rte_mempool_objhdr);
 ^
dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h:149:1: warning: type defaults to ‘int’ in declaration of ‘STAILQ_HEAD’ [enabled by default]
dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h:149:1: warning: parameter names (without types) in function declaration [enabled by default]
dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h:168:1: warning: data definition has no type or storage class [enabled by default]
 STAILQ_HEAD(rte_mempool_memhdr_list, rte_mempool_memhdr);
 ^
dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h:168:1: warning: type defaults to ‘int’ in declaration of ‘STAILQ_HEAD’ [enabled by default]
dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h:168:1: warning: parameter names (without types) in function declaration [enabled by default]
dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h:174:2: warning: ‘struct rte_mempool_memhdr’ declared inside parameter list [enabled by default]
  void *opaque);
  ^
dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h:174:2: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default]
dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h:183:2: error: expected specifier-qualifier-list before ‘STAILQ_ENTRY’
  STAILQ_ENTRY(rte_mempool_memhdr) next; /**< Next in list. */
  ^
dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h:250:33: error: field ‘elt_list’ has incomplete type
  struct rte_mempool_objhdr_list elt_list; /**< List of objects in pool */
                                 ^
/dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h:252:33: error: field ‘mem_list’ has incomplete type
  struct rte_mempool_memhdr_list mem_list; /**< List of memory chunks */
                                 ^
dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h: In function ‘rte_mempool_from_obj’:
dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h:329:12: error: ‘struct rte_mempool_objhdr’ has no member named ‘mp’
  return hdr->mp;
            ^
dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h: In function ‘rte_mempool_virt2iova’:
dpdk-stable-18.11.2/x86_64-native-linuxapp-gcc/include/rte_mempool.h:1614:12: error: ‘const struct rte_mempool_objhdr’ has no member named ‘iova’

I tried to run your code with dpdk 18.11.2 and it had no problem. but when I change it to suricata 5.0.0 it got a problem above.

Could you give me more comment for this situation?
Thanks in advance!

The ports always returns 0 when I run suricata

Hi Vipin, thanks for your efforts!

I have installed DPDK-19.11.1 LTS successfully as follow：

I have also installed Suricata-4.1.4 on Ubuntu 16.04 LTS，but when I run suricata，the dpdk ports always returns 0：

But I run an example(dpdk/dpdk-stable-19.11.3/examples/bond/build/bond_app)，the function rte_eth_dev_count_avail() returns the ports I bind by dpdk-devbind.py.

And the NIC I have boned as follow:

So I want to know how to solve this problem？Thank you for your replay.

Package not logged to fast.log

Hi
The Title is my ploblem.Here are some details.
I installed and tested the program on a six port physical machine. The first four network ports are bound with dpdk. I bind the image port on a switch to the first network port of dpdk, and then run the program in the way of readme. However, there is no log output to fast.log. So I bound the image port to another normal network port that is not bound to dpdk, and he will output the log to fast.log normally.

Thanks
Chen

Maybe useful:
[EAL]
-c 1
--log-level=eal,1
--file-prefix=suricata_1
-m=128
-w=0000:01:00.0
#-w=05:00.0

[PORT-0]
rx-queues=2
tx-queues=2

0, 3, 5, tep

rss-tuple=3
jumbo=no
mtu=1500
core=0

#[PORT-1]
#rx-queues=2
#tx-queues=2

0, 3, 5, tep

#rss-tuple=3
#jumbo=no
#mtu=1500
#core=0

* buffer overflow detected *

i have installed DPDK_SURICATA-4_1_1. if i don't create .pid file directory (/usr/local/var/run/suricata) it works fine. but when i create the directory it gives buffer overflow and core dumps. below are the logs:

#########################################################################
16/2/2021 -- 23:58:21 - - DPDK Mode selected
16/2/2021 -- 23:58:21 - - (name:suricatareassembly)
16/2/2021 -- 23:58:21 - - (n:8000)
16/2/2021 -- 23:58:21 - - This is Suricata version 4.1.4 RELEASE
eth_i40e_dev_init(): >>
i40e_pf_reset(): Core and Global modules ready 0
i40e_init_shared_code(): i40e_init_shared_code
i40e_set_mac_type(): i40e_set_mac_type

i40e_set_mac_type(): i40e_set_mac_type found mac: 3, returns: 0
i40e_init_nvm(): i40e_init_nvm
i40e_allocate_dma_mem_d(): memzone i40e_dma_9552954295447965524 allocated with physical address: 135765086208
i40e_allocate_dma_mem_d(): memzone i40e_dma_10537752058101462299 allocated with physical address: 135765078016
i40e_allocate_dma_mem_d(): memzone i40e_dma_4467097119028756380 allocated with physical address: 135765069824
i40e_allocate_dma_mem_d(): memzone i40e_dma_11094369750391936087 allocated with physical address: 135765061632
i40e_allocate_dma_mem_d(): memzone i40e_dma_2357206860469928774 allocated with physical address: 135765053440
i40e_allocate_dma_mem_d(): memzone i40e_dma_15517435520294160827 allocated with physical address: 135765045248
i40e_allocate_dma_mem_d(): memzone i40e_dma_1944565249397310739 allocated with physical address: 135765037056
i40e_allocate_dma_mem_d(): memzone i40e_dma_8555359644618513928 allocated with physical address: 135765028864
i40e_allocate_dma_mem_d(): memzone i40e_dma_17303758510226264824 allocated with physical address: 135765020672
i40e_allocate_dma_mem_d(): memzone i40e_dma_16700232228067893249 allocated with physical address: 135765012480
i40e_allocate_dma_mem_d(): memzone i40e_dma_10154589141307910194 allocated with physical address: 135765004288
i40e_allocate_dma_mem_d(): memzone i40e_dma_14752547576346201973 allocated with physical address: 135764996096
i40e_allocate_dma_mem_d(): memzone i40e_dma_7352608922326822641 allocated with physical address: 135764987904
i40e_allocate_dma_mem_d(): memzone i40e_dma_4484603879425425038 allocated with physical address: 135764979712
i40e_allocate_dma_mem_d(): memzone i40e_dma_13988654943656499604 allocated with physical address: 135764971520
i40e_allocate_dma_mem_d(): memzone i40e_dma_10059975339079523170 allocated with physical address: 135764963328
i40e_allocate_dma_mem_d(): memzone i40e_dma_15042036484702135092 allocated with physical address: 135764955136
i40e_allocate_dma_mem_d(): memzone i40e_dma_2800802514004336181 allocated with physical address: 135764946944
i40e_allocate_dma_mem_d(): memzone i40e_dma_8533402497044354155 allocated with physical address: 135764938752
i40e_allocate_dma_mem_d(): memzone i40e_dma_17073135590976328762 allocated with physical address: 135764930560
i40e_allocate_dma_mem_d(): memzone i40e_dma_3928742064707388522 allocated with physical address: 135764922368
i40e_allocate_dma_mem_d(): memzone i40e_dma_12442175789223829241 allocated with physical address: 135764914176
i40e_allocate_dma_mem_d(): memzone i40e_dma_7847775647923605354 allocated with physical address: 135764905984
i40e_allocate_dma_mem_d(): memzone i40e_dma_9466607039228933503 allocated with physical address: 135764897792
i40e_allocate_dma_mem_d(): memzone i40e_dma_2461807414213920453 allocated with physical address: 135764889600
i40e_allocate_dma_mem_d(): memzone i40e_dma_12011250448203024952 allocated with physical address: 135764881408
i40e_allocate_dma_mem_d(): memzone i40e_dma_16319023236189038430 allocated with physical address: 135764873216
i40e_allocate_dma_mem_d(): memzone i40e_dma_13639392030151329575 allocated with physical address: 135764865024
i40e_allocate_dma_mem_d(): memzone i40e_dma_10074149337934940570 allocated with physical address: 135764856832
i40e_allocate_dma_mem_d(): memzone i40e_dma_5564580544099575099 allocated with physical address: 135764848640
i40e_allocate_dma_mem_d(): memzone i40e_dma_13204489795781727554 allocated with physical address: 135764840448
i40e_allocate_dma_mem_d(): memzone i40e_dma_7050563908195163685 allocated with physical address: 135764832256
i40e_allocate_dma_mem_d(): memzone i40e_dma_9287623076354258551 allocated with physical address: 135764824064
i40e_allocate_dma_mem_d(): memzone i40e_dma_14158507071461961772 allocated with physical address: 135764819968
i40e_allocate_dma_mem_d(): memzone i40e_dma_16012500873323633473 allocated with physical address: 135764811776
i40e_allocate_dma_mem_d(): memzone i40e_dma_1471706944976173771 allocated with physical address: 135764803584
i40e_allocate_dma_mem_d(): memzone i40e_dma_615921738379914772 allocated with physical address: 135764795392
i40e_allocate_dma_mem_d(): memzone i40e_dma_18435876694093462030 allocated with physical address: 135764787200
i40e_allocate_dma_mem_d(): memzone i40e_dma_2354017733972504235 allocated with physical address: 135764779008
i40e_allocate_dma_mem_d(): memzone i40e_dma_9837575359350738263 allocated with physical address: 135764770816
i40e_allocate_dma_mem_d(): memzone i40e_dma_16759891359292240424 allocated with physical address: 135764762624
i40e_allocate_dma_mem_d(): memzone i40e_dma_5863992001294989850 allocated with physical address: 135764754432
i40e_allocate_dma_mem_d(): memzone i40e_dma_17236571951114475460 allocated with physical address: 135764746240
i40e_allocate_dma_mem_d(): memzone i40e_dma_4972558883524263419 allocated with physical address: 135764738048
i40e_allocate_dma_mem_d(): memzone i40e_dma_10736697405764145994 allocated with physical address: 135764729856
i40e_allocate_dma_mem_d(): memzone i40e_dma_972367950042002850 allocated with physical address: 135764721664
i40e_allocate_dma_mem_d(): memzone i40e_dma_2848085627518486245 allocated with physical address: 135764713472
i40e_allocate_dma_mem_d(): memzone i40e_dma_3591231882908821515 allocated with physical address: 135764705280
i40e_allocate_dma_mem_d(): memzone i40e_dma_9978037698645871949 allocated with physical address: 135764697088
i40e_allocate_dma_mem_d(): memzone i40e_dma_15971387182153999535 allocated with physical address: 135764688896
i40e_allocate_dma_mem_d(): memzone i40e_dma_13931107585915101655 allocated with physical address: 135764680704
i40e_allocate_dma_mem_d(): memzone i40e_dma_787816179504078811 allocated with physical address: 135764672512
i40e_allocate_dma_mem_d(): memzone i40e_dma_2701041660615218482 allocated with physical address: 135764664320
i40e_allocate_dma_mem_d(): memzone i40e_dma_10371771098141526418 allocated with physical address: 135764656128
i40e_allocate_dma_mem_d(): memzone i40e_dma_16947982948653663107 allocated with physical address: 135764647936
i40e_allocate_dma_mem_d(): memzone i40e_dma_2443724648024132454 allocated with physical address: 135764639744
i40e_allocate_dma_mem_d(): memzone i40e_dma_12653843005149675882 allocated with physical address: 135764631552
i40e_allocate_dma_mem_d(): memzone i40e_dma_12862643226729966527 allocated with physical address: 135764623360
i40e_allocate_dma_mem_d(): memzone i40e_dma_2890089386044204262 allocated with physical address: 135764615168
i40e_allocate_dma_mem_d(): memzone i40e_dma_15165409126234584986 allocated with physical address: 135764606976
i40e_allocate_dma_mem_d(): memzone i40e_dma_12778788956451624888 allocated with physical address: 135764598784
i40e_allocate_dma_mem_d(): memzone i40e_dma_10869252416429894984 allocated with physical address: 135764590592
i40e_allocate_dma_mem_d(): memzone i40e_dma_8172481245372722343 allocated with physical address: 135764582400
i40e_allocate_dma_mem_d(): memzone i40e_dma_17078639780072077030 allocated with physical address: 135764574208
i40e_allocate_dma_mem_d(): memzone i40e_dma_6085203697319240888 allocated with physical address: 135764566016
i40e_allocate_dma_mem_d(): memzone i40e_dma_1508110770577353587 allocated with physical address: 135764557824
i40e_acquire_nvm(): i40e_acquire_nvm
i40e_aq_request_resource(): i40e_aq_request_resource
i40e_read_nvm_word_aq(): i40e_read_nvm_word_aq
i40e_read_nvm_aq(): i40e_read_nvm_aq
i40e_aq_read_nvm(): i40e_aq_read_nvm
i40e_release_nvm(): i40e_release_nvm
i40e_aq_release_resource(): i40e_aq_release_resource
i40e_acquire_nvm(): i40e_acquire_nvm
i40e_aq_request_resource(): i40e_aq_request_resource
i40e_read_nvm_word_aq(): i40e_read_nvm_word_aq
i40e_read_nvm_aq(): i40e_read_nvm_aq
i40e_aq_read_nvm(): i40e_aq_read_nvm
i40e_release_nvm(): i40e_release_nvm
i40e_aq_release_resource(): i40e_aq_release_resource
i40e_acquire_nvm(): i40e_acquire_nvm
i40e_aq_request_resource(): i40e_aq_request_resource
i40e_read_nvm_word_aq(): i40e_read_nvm_word_aq
i40e_read_nvm_aq(): i40e_read_nvm_aq
i40e_aq_read_nvm(): i40e_aq_read_nvm
i40e_release_nvm(): i40e_release_nvm
i40e_aq_release_resource(): i40e_aq_release_resource
i40e_acquire_nvm(): i40e_acquire_nvm
i40e_aq_request_resource(): i40e_aq_request_resource
i40e_read_nvm_word_aq(): i40e_read_nvm_word_aq
i40e_read_nvm_aq(): i40e_read_nvm_aq
i40e_aq_read_nvm(): i40e_aq_read_nvm
i40e_release_nvm(): i40e_release_nvm
i40e_aq_release_resource(): i40e_aq_release_resource
i40e_acquire_nvm(): i40e_acquire_nvm
i40e_aq_request_resource(): i40e_aq_request_resource
i40e_read_nvm_word_aq(): i40e_read_nvm_word_aq
i40e_read_nvm_aq(): i40e_read_nvm_aq
i40e_aq_read_nvm(): i40e_aq_read_nvm
i40e_release_nvm(): i40e_release_nvm
i40e_aq_release_resource(): i40e_aq_release_resource
i40e_acquire_nvm(): i40e_acquire_nvm
i40e_aq_request_resource(): i40e_aq_request_resource
i40e_read_nvm_word_aq(): i40e_read_nvm_word_aq
i40e_read_nvm_aq(): i40e_read_nvm_aq
i40e_aq_read_nvm(): i40e_aq_read_nvm
i40e_release_nvm(): i40e_release_nvm
i40e_aq_release_resource(): i40e_aq_release_resource
i40e_aq_release_resource(): i40e_aq_release_resource
eth_i40e_dev_init(): FW 4.1 API 1.9 NVM 04.01.01 eetrack 80001fa0
i40e_enable_extended_tag(): Extended Tag has already been enabled
i40e_check_write_reg(): [0x002507c0] original: 0x00000000
i40e_check_write_reg(): [0x002507c0] after: 0x00000000
i40e_check_write_reg(): [0x002507e0] original: 0x00060606
i40e_check_write_reg(): [0x002507e0] after: 0x00060606
i40e_check_write_reg(): [0x00250800] original: 0x00000000
i40e_check_write_reg(): [0x00250800] after: 0x00000000
i40e_check_write_reg(): [0x00250820] original: 0x00060606
i40e_check_write_reg(): [0x00250820] after: 0x00060606
i40e_check_write_reg(): [0x00250840] original: 0x00000000
i40e_check_write_reg(): [0x00250840] after: 0x00000000
i40e_check_write_reg(): [0x00250860] original: 0x00060606
i40e_check_write_reg(): [0x00250860] after: 0x00060606
i40e_check_write_reg(): [0x00250880] original: 0x80000000
i40e_check_write_reg(): [0x00250880] after: 0x80000000
i40e_check_write_reg(): [0x002508a0] original: 0x00060607
i40e_check_write_reg(): [0x002508a0] after: 0x00060607
i40e_check_write_reg(): [0x002508c0] original: 0x00000000
i40e_check_write_reg(): [0x002508c0] after: 0x00000000
i40e_check_write_reg(): [0x002508e0] original: 0x00060600
i40e_check_write_reg(): [0x002508e0] after: 0x00060600
i40e_check_write_reg(): [0x00250900] original: 0x00000000
i40e_check_write_reg(): [0x00250900] after: 0x00000000
i40e_check_write_reg(): [0x00250920] original: 0x00060600
i40e_check_write_reg(): [0x00250920] after: 0x00060600
i40e_check_write_reg(): [0x002509c0] original: 0x00000000
i40e_check_write_reg(): [0x002509c0] after: 0x00000000
i40e_check_write_reg(): [0x002509e0] original: 0x0007fffe
i40e_check_write_reg(): [0x002509e0] after: 0x0007fffe
i40e_check_write_reg(): [0x00250a00] original: 0x00000000
i40e_check_write_reg(): [0x00250a00] after: 0x00000000
i40e_check_write_reg(): [0x00250a20] original: 0x0007fffe
i40e_check_write_reg(): [0x00250a20] after: 0x0007fffe
i40e_check_write_reg(): [0x00250a40] original: 0x00000000
i40e_check_write_reg(): [0x00250a40] after: 0x00000000
i40e_check_write_reg(): [0x00250a60] original: 0x0007fffe
i40e_check_write_reg(): [0x00250a60] after: 0x0007fffe
i40e_check_write_reg(): [0x00250a80] original: 0x00000000
i40e_check_write_reg(): [0x00250a80] after: 0x00000000
i40e_check_write_reg(): [0x00250aa0] original: 0x0007fffe
i40e_check_write_reg(): [0x00250aa0] after: 0x0007fffe
i40e_check_write_reg(): [0x00250ac0] original: 0x00000000
i40e_check_write_reg(): [0x00250ac0] after: 0x00000000
i40e_check_write_reg(): [0x00250ae0] original: 0x0007fffe
i40e_check_write_reg(): [0x00250ae0] after: 0x0007fffe
i40e_check_write_reg(): [0x00250b00] original: 0x80000000
i40e_check_write_reg(): [0x00250b00] after: 0x80000000
i40e_check_write_reg(): [0x00250b20] original: 0x0007ffff
i40e_check_write_reg(): [0x00250b20] after: 0x0007ffff
i40e_check_write_reg(): [0x00250b40] original: 0x00000000
i40e_check_write_reg(): [0x00250b40] after: 0x00000000
i40e_check_write_reg(): [0x00250b60] original: 0x0007fff8
i40e_check_write_reg(): [0x00250b60] after: 0x0007fff8
i40e_check_write_reg(): [0x00250b80] original: 0x00000000
i40e_check_write_reg(): [0x00250b80] after: 0x00000000
i40e_check_write_reg(): [0x00250ba0] original: 0x0007fff8
i40e_check_write_reg(): [0x00250ba0] after: 0x0007fff8
i40e_check_write_reg(): [0x00250fc0] original: 0x00004000
i40e_check_write_reg(): [0x00250fc0] after: 0x00004000
i40e_check_write_reg(): [0x00250fe0] original: 0x00000000
i40e_check_write_reg(): [0x00250fe0] after: 0x00000000
eth_i40e_dev_init(): Global register 0x0026c7a0 is changed with 0x28
i40e_configure_registers(): Read from 0x26ce00: 0x20000200
i40e_configure_registers(): Read from 0x26ce08: 0x13f0200
i40e_configure_registers(): Device 0x37d3 skips GL_SWR_PM_UP_THR value fixup
i40e_acquire_nvm(): i40e_acquire_nvm
i40e_aq_request_resource(): i40e_aq_request_resource
i40e_aq_read_nvm(): i40e_aq_read_nvm
i40e_release_nvm(): i40e_release_nvm
i40e_aq_release_resource(): i40e_aq_release_resource
i40e_pf_parameter_init(): No queue or VSI left for VMDq
i40e_allocate_dma_mem_d(): memzone i40e_dma_1069257075810229233 allocated with physical address: 135764492288
i40e_validate_mac_addr(): i40e_validate_mac_addr
i40e_vlan_tpid_set_by_registers(): Debug read from I40E_GL_SWT_L2TAGCTRL[3]: 0x81000682
i40e_vlan_tpid_set_by_registers(): No need to write
i40e_update_default_filter_setting(): Cannot remove the default macvlan filter
i40e_vsi_get_bw_config(): VSI bw limit:0
i40e_vsi_get_bw_config(): VSI max_bw:0
i40e_vsi_get_bw_config(): VSI TC0:share credits 1
i40e_vsi_get_bw_config(): VSI TC0:credits 0
i40e_vsi_get_bw_config(): VSI TC0: max credits: 0
i40e_vsi_get_bw_config(): VSI TC1:share credits 0
i40e_vsi_get_bw_config(): VSI TC1:credits 0
i40e_vsi_get_bw_config(): VSI TC1: max credits: 0
i40e_vsi_get_bw_config(): VSI TC2:share credits 0
i40e_vsi_get_bw_config(): VSI TC2:credits 0
i40e_vsi_get_bw_config(): VSI TC2: max credits: 0
i40e_vsi_get_bw_config(): VSI TC3:share credits 0
i40e_vsi_get_bw_config(): VSI TC3:credits 0
i40e_vsi_get_bw_config(): VSI TC3: max credits: 0
i40e_vsi_get_bw_config(): VSI TC4:share credits 0
i40e_vsi_get_bw_config(): VSI TC4:credits 0
i40e_vsi_get_bw_config(): VSI TC4: max credits: 0
i40e_vsi_get_bw_config(): VSI TC5:share credits 0
i40e_vsi_get_bw_config(): VSI TC5:credits 0
i40e_vsi_get_bw_config(): VSI TC5: max credits: 0
i40e_vsi_get_bw_config(): VSI TC6:share credits 0
i40e_vsi_get_bw_config(): VSI TC6:credits 0
i40e_vsi_get_bw_config(): VSI TC6: max credits: 0
i40e_vsi_get_bw_config(): VSI TC7:share credits 0
i40e_vsi_get_bw_config(): VSI TC7:credits 0
i40e_vsi_get_bw_config(): VSI TC7: max credits: 0
i40e_pf_setup(): Hardware capability of hash lookup table size: 512
i40e_update_flow_control(): Link auto negotiation not completed
i40e_dcb_init_configure(): Failed to stop lldp
i40e_acquire_nvm(): i40e_acquire_nvm
i40e_aq_request_resource(): i40e_aq_request_resource
i40e_aq_read_nvm(): i40e_aq_read_nvm
i40e_release_nvm(): i40e_release_nvm
i40e_aq_release_resource(): i40e_aq_release_resource
i40e_acquire_nvm(): i40e_acquire_nvm
i40e_aq_request_resource(): i40e_aq_request_resource
i40e_aq_read_nvm(): i40e_aq_read_nvm
i40e_release_nvm(): i40e_release_nvm
i40e_aq_release_resource(): i40e_aq_release_resource
i40e_acquire_nvm(): i40e_acquire_nvm
i40e_aq_request_resource(): i40e_aq_request_resource
i40e_aq_read_nvm(): i40e_aq_read_nvm
i40e_release_nvm(): i40e_release_nvm
i40e_aq_release_resource(): i40e_aq_release_resource
i40e_acquire_nvm(): i40e_acquire_nvm
i40e_aq_request_resource(): i40e_aq_request_resource
i40e_aq_read_nvm(): i40e_aq_read_nvm
i40e_release_nvm(): i40e_release_nvm
i40e_aq_release_resource(): i40e_aq_release_resource
i40e_acquire_nvm(): i40e_acquire_nvm
i40e_aq_request_resource(): i40e_aq_request_resource
i40e_aq_read_nvm(): i40e_aq_read_nvm
i40e_release_nvm(): i40e_release_nvm
i40e_aq_release_resource(): i40e_aq_release_resource
i40e_pf_host_init(): >>
i40e_update_vsi_stats(): ***************** VSI[15] stats start *******************
i40e_update_vsi_stats(): rx_bytes: 0
i40e_update_vsi_stats(): rx_unicast: 0
i40e_update_vsi_stats(): rx_multicast: 0
i40e_update_vsi_stats(): rx_broadcast: 0
i40e_update_vsi_stats(): rx_discards: 0
i40e_update_vsi_stats(): rx_unknown_protocol: 0
i40e_update_vsi_stats(): tx_bytes: 0
i40e_update_vsi_stats(): tx_unicast: 0
i40e_update_vsi_stats(): tx_multicast: 0
i40e_update_vsi_stats(): tx_broadcast: 0
i40e_update_vsi_stats(): tx_discards: 0
i40e_update_vsi_stats(): tx_errors: 0
i40e_update_vsi_stats(): ***************** VSI[15] stats end *******************
16/2/2021 -- 23:58:22 - - this looks like a good signaturei (2221000), try to add to DPDK ACL!
16/2/2021 -- 23:58:22 - - - alproto (1) mask (0) id (0) action (1)
16/2/2021 -- 23:58:22 - - -- proto (flags-0)