pmd | An extensible multilanguage static code analyzer | Code Analyzer library

OK, I found the source of the problem. You should replace artifactoryDeploy with artifactoryPublish command.

[EDIT-1] clarification of using same interface for DPDK and Kernel routing

Answer> as discussed over comments please refer to DPDKD + kernel on same interface

Based on the information shared there are multiple questions to the single query I'm trying to bypass all traffic to the PMD I'm currently developing. Addressing each one separately below

1. question 1: using dpdk-l2fwd example application

Answer> DPDK application l2fwd application makes use of basic APi with almost no HW offloads. Based on your environment (I have a board with one ethernet interface (eth0)), the right set of parameters should be -p 0x1 --no-mac-updating -T 1. This will configure the application to receive and transmit packet using single DPDK interface (that is eth0 on your board).

Note: DPDK Application can work with DPDK PMD both physical and virtual

1. question 2: I tried to use net_tap, using the following command:

Answer> If the intend is to intercept the traffic from physical and then forward to tap interface, then one needs modify the eal arguments as ./build/l2fwd --vdev=net_tap0,iface="my_eth0" -- -p 0x3 -T 1 --no-mac-updating. This will allow the application to probe physical NXP interface (eth0) and make use of Linux TAP interface as secondary interface. Thus any traffic from NXP and TAP will be cross connected such as NXP (eth0) <==> TAP (my_eth0)

1. question 3: ./usertools/dpdk-devbind.py --status returns empty

Answer> Form the dpdk site supported NIC list NXP dpaa, dpaa2, enetc, enetfec, pfe. Cross checking the kernel driver fsl_dpaa2_eth I think it is safe to assume dpaa2 PMD is supported. As you have mentioned the NIC is not enumerated, it looks like there are certain caveats to such model revision, supported board, BSP package, vendor-sub vendor ID check etc. More details can be found Board Support Package, and DPAA2 NIC guide

Debug & Alternative solutions:

1. To start with use the Kernel Driver to bring in packets
2. Use extra logging and debug to identify why the NIC is shown in the application

Approach 1:

1. Make sure the NIC is bind with kernel driver fsl_dpaa2_eth.
2. ensure NIC is connected and link is up with ethtool eth0
3. set to promiscous mode with ifconfig eth0 promisc up
4. start DPDK application with PCAP PMD, ./build/l2fwd --vdev=net_pcap0,iface=eth0 -- -p 1 --no-mac-updating -T 1
5. Check packet are received and redirected to PCAP eth0 PMD by checking the statistics.

Approach 2:

1. Ideally the NIC should be categorized under network device to be probed by debind.py.
2. Check the device details using lshw -c net -businfo for network.
3. try checking with lspci -Dvmmnnk [PCIe BUS:Slot:Function id] for network details.
4. If above details does not show up as network device this might be reason for not getting listed.

• Suggestions or workaround: You can try to forcefully bind with igb_uio or vfio-pci (I am not much famialr with NXP SoC) by dpdk-devbind -b vfio-pci [PCIe S:B:F]. Then cross check with lspci -ks [PCIe S:B:F]. Once successfully done, one can start dpdk l2fwd in PMD debug mode with ./build/l2fwd -a [PCIe S:B:F] --log-level=pmd,8 -- -p 1 --no-mac-updating | more. Thus by intercepting and interpreting the logs one can identify what is going

Note:

1. It is assumed the application is build with static libraries and not dynamic. To build with static libraries use make static for l2fwd.
2. For the described use case recommended application is basicfwd/skeleton rather than l2fwd.

The results of virt_to_pfn(kaddr) and virt_to_page(kaddr) are valid if and only if virt_addr_valid(kaddr) is true. That is only true if kaddr is in the linear-mapped (lowmem) region of kernel virtual address space.

pfn_valid(virt_to_pfn(kaddr)) is not equivalent to virt_addr_valid(kaddr). virt_addr_valid(kaddr) implies pfn_valid(virt_to_pfn(kaddr)) but pfn_valid(virt_to_pfn(kaddr)) does not imply virt_addr_valid(kaddr).

You're using a pre-warmed image

You'd need to bundle the checkstyle.xml within your plugin's resources folder, so when you ship it, you can always access it from within the plugin code.

Basically, you need to put the config under src/main/resources/checkstyle.xml of the plugin and then access it like this:

There are very few deprecated rules in the Apex module: https://pmd.github.io/latest/pmd_rules_apex.html

PMD rules are usually not deprecated without a replacement. For instance AvoidDmlStatementsInLoops is replaced by OperationWithLimitsInLoops, as documented. Sometimes several rules are consolidated into a single one, which is the case for those 3 performance rules. You might get the impression that many rules are deprecated, but no functionality is lost, and the newer rules are generally more easily extensible.

If you are seeing many deprecation warnings, it may be because you are referencing those rules through deprecated rulesets. For instance, if you write

The problem is the password encoder. It is required to build the auto-configured UserDetailsService that you inject in the contructor of the class.

You can break the cycle by making the bean factory method static:

I solved the problem by changing docker volume mount point to Jenkins WORKSPACE path.

It turns out that the eclipse-pmd plugin (which I found in C:\Users\{username}\.p2\pool\plugins) comes packaged with its own version of PMD, which in this case is 6.28.0.

This doesn't fully explain the discrepency, since the AvoidUncheckedExceptionsInSignatures rule has been around since PMD 6.13.0, but I'm happy enough to blame the difference in versions for the difference in output.