please help backporting some patches to stable release 20.11.5

please help backporting some patches to stable release 20.11.5

[luca.boccassi]

Hi commit authors (and maintainers),

Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
I didn't apply following commits from DPDK main to 20.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 20.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 2022/03/18.

You can find the a temporary work-in-progress branch of the coming 20.11.5
release at:
    https://github.com/bluca/dpdk-stable
It is recommended to backport on top of that to minimize further conflicts or
misunderstandings.

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 20.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
f65c7fbcec  Devendra Singh Rawat net/qede: fix Rx bulk
c1d1b94eec  Gerry Gribbon    app/regex: fix number of matches
a058de216c  Gregory Etelson  app/testpmd: fix GTP header parsing in checksum engine

please help backporting some patches to stable release 20.11.5

[luca.boccassi]

Hi commit authors (and maintainers),

Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
I didn't apply following commits from DPDK main to 20.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 20.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 03/16/22.

You can find the a temporary work-in-progress branch of the coming 20.11.5
release at:
    https://github.com/bluca/dpdk-stable
It is recommended to backport on top of that to minimize further conflicts or
misunderstandings.

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 20.11] foo/bar: fix baz

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

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

Thanks.

Luca Boccassi

---
dc065d6efd  Adham Masarwah   net/mlx5: fix destroying empty matchers list
655c3c26c1  Dmitry Kozlyuk   net/mlx5: fix initial link status detection
17f95513ad  Dmitry Kozlyuk   net/mlx5: fix link status change detection
4bab7ea60c  Karl Bonde Torp  build: fix build on FreeBSD with Meson 0.61.1
9267617bb0  Shun Hao         net/mlx5: fix meter policy creation assert
20659eb380  Wei Huang        raw/ifpga: fix interrupt handle allocation

please help backporting some patches to stable release 20.11.5

[luca.boccassi]

Hi commit authors (and maintainers),

Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
I didn't apply following commits from DPDK main to 20.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 20.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 03/07/22.

You can find the a temporary work-in-progress branch of the coming 20.11.5
release at:
    https://github.com/bluca/dpdk-stable
It is recommended to backport on top of that to minimize further conflicts or
misunderstandings.

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 20.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
033904450b  Chengwen Feng    dma/hisilicon: use common PCI device naming
6be4c57add  Michael Baum     net/mlx5: fix errno update in shared context creation
dcbaafdc8f  Michael Baum     net/mlx5: fix sibling device config check
a501609ea6  Pablo de Lara    crypto/ipsec_mb: fix length and offset settings

RE: please help backporting some patches to stable release 20.11.5

[De Lara Guarch, Pablo]

Hi Luca,

> -----Original Message-----
> From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> Sent: Monday, February 28, 2022 9:32 PM
> Cc: Akhil Goyal <akhil.goyal@nxp.com>; Chengwen Feng
> <fengchengwen@huawei.com>; Zhang, Roy Fan <roy.fan.zhang@intel.com>;
> Laatz, Kevin <kevin.laatz@intel.com>; Khoa To <khot@microsoft.com>; Matan
> Azrad <matan@nvidia.com>; Michael Baum <michaelba@nvidia.com>; De Lara
> Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Shahaf Shuler
> <shahafs@nvidia.com>; Tal Shnaiderman <talshn@nvidia.com>; Viacheslav
> Ovsiienko <viacheslavo@nvidia.com>; Yongseok Koh <yskoh@mellanox.com>
> Subject: please help backporting some patches to stable release 20.11.5
> 
> Hi commit authors (and maintainers),
> 
> Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
> I didn't apply following commits from DPDK main to 20.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 20.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 03/07/22.
> 
> You can find the a temporary work-in-progress branch of the coming 20.11.5
> release at:
>     https://github.com/bluca/dpdk-stable
> It is recommended to backport on top of that to minimize further conflicts or
> misunderstandings.
> 
> 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 20.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 20.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 20.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Luca Boccassi
> 
> ---
> 033904450b  Chengwen Feng    dma/hisilicon: use common PCI device naming
> 6be4c57add  Michael Baum     net/mlx5: fix errno update in shared context
> creation
> dcbaafdc8f  Michael Baum     net/mlx5: fix sibling device config check
> a501609ea6  Pablo de Lara    crypto/ipsec_mb: fix length and offset settings

Apologies, but looks like the commit "crypto/ipsec_mb: fix length and offset settings"
Has introduced a bug which I am fixing now. I will send a fix to the dev list soon,
but I am wondering if it's better to combine it into a single one and push it to the stable list instead of backporting two commits?

Thanks,
Pablo

Re: please help backporting some patches to stable release 20.11.5

[Luca Boccassi]

On Tue, 8 Mar 2022 at 17:44, De Lara Guarch, Pablo
<pablo.de.lara.guarch@intel.com> wrote:
>
> Hi Luca,
>
> > -----Original Message-----
> > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> > Sent: Monday, February 28, 2022 9:32 PM
> > Cc: Akhil Goyal <akhil.goyal@nxp.com>; Chengwen Feng
> > <fengchengwen@huawei.com>; Zhang, Roy Fan <roy.fan.zhang@intel.com>;
> > Laatz, Kevin <kevin.laatz@intel.com>; Khoa To <khot@microsoft.com>; Matan
> > Azrad <matan@nvidia.com>; Michael Baum <michaelba@nvidia.com>; De Lara
> > Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Shahaf Shuler
> > <shahafs@nvidia.com>; Tal Shnaiderman <talshn@nvidia.com>; Viacheslav
> > Ovsiienko <viacheslavo@nvidia.com>; Yongseok Koh <yskoh@mellanox.com>
> > Subject: please help backporting some patches to stable release 20.11.5
> >
> > Hi commit authors (and maintainers),
> >
> > Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
> > I didn't apply following commits from DPDK main to 20.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 20.11 branch, or
> >     - Indicate that the patch should not be backported
> >
> > Please do either of the above by 03/07/22.
> >
> > You can find the a temporary work-in-progress branch of the coming 20.11.5
> > release at:
> >     https://github.com/bluca/dpdk-stable
> > It is recommended to backport on top of that to minimize further conflicts or
> > misunderstandings.
> >
> > 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 20.11] foo/bar: fix baz
> >
> > With git format-patch, this can be achieved by appending the parameter:
> >     --subject-prefix='PATCH 20.11'
> >
> > Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> >
> > FYI, branch 20.11 is located at tree:
> >    https://git.dpdk.org/dpdk-stable
> >
> > Thanks.
> >
> > Luca Boccassi
> >
> > ---
> > 033904450b  Chengwen Feng    dma/hisilicon: use common PCI device naming
> > 6be4c57add  Michael Baum     net/mlx5: fix errno update in shared context
> > creation
> > dcbaafdc8f  Michael Baum     net/mlx5: fix sibling device config check
> > a501609ea6  Pablo de Lara    crypto/ipsec_mb: fix length and offset settings
>
> Apologies, but looks like the commit "crypto/ipsec_mb: fix length and offset settings"
> Has introduced a bug which I am fixing now. I will send a fix to the dev list soon,
> but I am wondering if it's better to combine it into a single one and push it to the stable list instead of backporting two commits?

Hi,

Please send the fix separately, so that we can better track the main
branch version. If the fix doesn't get into 22.03, we can postpone
both backports until the next stable release, to avoid introducing
regressions.

Kind regards,
Luca Boccassi

RE: please help backporting some patches to stable release 20.11.5

[De Lara Guarch, Pablo]

Hi Luca,

> -----Original Message-----
> From: Luca Boccassi <luca.boccassi@gmail.com>
> Sent: Wednesday, March 9, 2022 12:14 AM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Cc: dpdk stable <stable@dpdk.org>
> Subject: Re: please help backporting some patches to stable release 20.11.5
> 
> On Tue, 8 Mar 2022 at 17:44, De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com> wrote:
> >
> > Hi Luca,
> >
> > > -----Original Message-----
> > > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> > > Sent: Monday, February 28, 2022 9:32 PM
> > > Cc: Akhil Goyal <akhil.goyal@nxp.com>; Chengwen Feng
> > > <fengchengwen@huawei.com>; Zhang, Roy Fan
> <roy.fan.zhang@intel.com>;
> > > Laatz, Kevin <kevin.laatz@intel.com>; Khoa To <khot@microsoft.com>;
> > > Matan Azrad <matan@nvidia.com>; Michael Baum
> <michaelba@nvidia.com>;
> > > De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Shahaf
> > > Shuler <shahafs@nvidia.com>; Tal Shnaiderman <talshn@nvidia.com>;
> > > Viacheslav Ovsiienko <viacheslavo@nvidia.com>; Yongseok Koh
> > > <yskoh@mellanox.com>
> > > Subject: please help backporting some patches to stable release
> > > 20.11.5
> > >
> > > Hi commit authors (and maintainers),
> > >
> > > Despite being selected by the DPDK maintenance tool
> > > ./devtools/git-log-fixes.sh I didn't apply following commits from
> > > DPDK main to 20.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 20.11 branch, or
> > >     - Indicate that the patch should not be backported
> > >
> > > Please do either of the above by 03/07/22.
> > >
> > > You can find the a temporary work-in-progress branch of the coming
> > > 20.11.5 release at:
> > >     https://github.com/bluca/dpdk-stable
> > > It is recommended to backport on top of that to minimize further
> > > conflicts or misunderstandings.
> > >
> > > 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 20.11] foo/bar: fix baz
> > >
> > > With git format-patch, this can be achieved by appending the parameter:
> > >     --subject-prefix='PATCH 20.11'
> > >
> > > Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> > >
> > > FYI, branch 20.11 is located at tree:
> > >    https://git.dpdk.org/dpdk-stable
> > >
> > > Thanks.
> > >
> > > Luca Boccassi
> > >
> > > ---
> > > 033904450b  Chengwen Feng    dma/hisilicon: use common PCI device
> naming
> > > 6be4c57add  Michael Baum     net/mlx5: fix errno update in shared context
> > > creation
> > > dcbaafdc8f  Michael Baum     net/mlx5: fix sibling device config check
> > > a501609ea6  Pablo de Lara    crypto/ipsec_mb: fix length and offset settings
> >
> > Apologies, but looks like the commit "crypto/ipsec_mb: fix length and offset
> settings"
> > Has introduced a bug which I am fixing now. I will send a fix to the
> > dev list soon, but I am wondering if it's better to combine it into a single one
> and push it to the stable list instead of backporting two commits?
> 
> Hi,
> 
> Please send the fix separately, so that we can better track the main branch
> version. If the fix doesn't get into 22.03, we can postpone both backports until
> the next stable release, to avoid introducing regressions.

Thanks for this. Both patches have been merged for 22.03, so I just sent the backported versions to the stable ML.

Pablo

> 
> Kind regards,
> Luca Boccassi

please help backporting some patches to stable release 20.11.5

[luca.boccassi]

Hi commit authors (and maintainers),

Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
I didn't apply following commits from DPDK main to 20.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 20.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 02/25/22.

You can find the a temporary work-in-progress branch of the coming 20.11.5
release at:
    https://github.com/bluca/dpdk-stable
It is recommended to backport on top of that to minimize further conflicts or
misunderstandings.

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 20.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
eb11edd9db  Alexander Kozyrev net/mlx5: fix meter capabilities reporting
728b6447e7  Alexander Kozyrev net/mlx5: fix MPRQ WQE size assertion
15174c40b7  Heinrich Kuhn    net/nfp: free HW ring memzone on queue release
5a2b22b40f  Huisong Li       net/hns3: fix mailbox wait time
2e1ecb460d  Jiawen Wu        net/txgbe: fix link up and down
10599cf83e  Michael Baum     common/mlx5: add minimum WQE size for striding RQ
8928997a13  Michael Baum     common/mlx5: fix error handling in multi-class probe
147f6fb42b  Michael Baum     net/mlx5: fix memory socket selection in ASO management
34776af600  Michael Baum     net/mlx5: fix MPRQ stride devargs adjustment
0947ed380f  Michael Baum     net/mlx5: improve stride parameter names
96c33cfb06  Min Hu (Connor)  net/hns3: fix Rx/Tx functions update
9cc217a283  Ruifeng Wang     config: add arch define for Arm