[dpdk-stable] please help backporting some patches to stable release 19.11.6

[luca.boccassi at gmail.com]

Hi commit authors (and maintainers),

I didn't apply following commits from DPDK main to 19.11
stable branch, as conflicts or build errors occur.

Can authors check your patches in the following list and either:
    - Backport your patches to the 19.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by the 16th of November.


Some notes on stable backports:

A backport should contain a reference to the DPDK main branch commit
in it's commit message in the following fashion:
    [ upstream commit <commit's dpdk main branch SHA-1 checksum> ]

For example:
    https://git.dpdk.org/dpdk-stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb

When sending the backported patch, please indicate the target branch in the
subject line, as we have multiple branches, for example:
    [PATCH 19.11] foo/bar: fix baz

With git format-patch, this can be achieved by appending the parameter:
    --subject-prefix='PATCH 19.11'

Send the backported patch to "stable at dpdk.org" but not "dev at dpdk.org".

FYI, branch 19.11 is located at tree:
   https://git.dpdk.org/dpdk-stable

Thanks.

Luca Boccassi

---
0e98d5e6d9  Chengchang Tang  net/hns3: fix packet type report in Rx
f9edada651  Chengchang Tang  net/hns3: fix Tx checksum outer header prepare
fb6eb9009f  Chengchang Tang  net/hns3: fix Tx checksum with fixed header length
ead06572bd  Jesse Brandeburg net/iavf: fix performance with writeback policy
c59898131b  Maxime Coquelin  vhost: validate index in async API
364eb0e466  Nithin Dabilpuram net/octeontx2: avoid per packet barrier with multi segment
fb4b7a131c  Patrick Fu       vhost: fix guest/host physical address conversion
1cbdad1bf2  Xueming Li       common/mlx5: get number of ports that can be bonded