Tianyu Li 36cb2f03ae dpdk: fix arm iavf rx vector path on 22.03
dpdk 22.03 introduces iavf driver but misses rx vector path on Arm.
This causes VF fail to receive packet when running VPP device test
with no-multi-seg configuration.

Add iavf basic Neon RX support to fix this.

Type: fix
Fixes: 2f132efc3caf ("dpdk: bump to DPDK v22.03")

Signed-off-by: Tianyu Li <tianyu.li@arm.com>
Change-Id: I75ae74c8060428cee0e1c235feab1246c014801e
2022-08-30 23:56:06 +00:00
..

Changes needed to DPDK are stored here as git patch files. Maintaining these
files using “git format-patch” and “git am” will make it simpler to manage
these changes. Patches made to DPDK should only be temporary until they are
accepted upstream and made available in the next DPDK release.

The following is the method used to generate these patches:

1. Git clone the package to a new directory:
 # git clone http://dpdk.org/git/dpdk dpdk

2. Create a branch based on the release you wish to patch.
Note, “git tag” will show you all the release tags. The following example is
for release tag “v2.2.0” and will create a branch named “two_dot_two”.
 # cd <root dir>
 # git checkout -b two_dot_two v2.2.0

3. Apply all the existing patches to this new branch.
 # git am </path/to/existing/patches/*>

4. Make your changes and commit your change to your repository.
 # <edit files>
 # git commit -s

5. Create the patch files with format-patch. This creates all the patch files
for your branch (two_dot_two), with your latest commits as the last ones.
 # git format-patch main..two_dot_two

6. Copy, add and commit the new patches into the patches directory.