please help backporting some patches to stable release 22.11.6

please help backporting some patches to stable release 22.11.6

[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 22.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 22.11 branch, or
    - Indicate that the patch should not be backported

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

You can find the a temporary work-in-progress branch of the coming 22.11.6
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 22.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
97039941b2  Frank Du         net/af_xdp: parse UMEM map info from mempool
ab1bb0c402  Peng Zhang       net/nfp: add check for numbers of VF representor port
fde2a1cb34  Rahul Bhansali   net/cnxk: postpone disabling NPC Rx and MCAM

Re: please help backporting some patches to stable release 22.11.6

[Luca Boccassi]

Hi,

That mempool patch introduces a new API, so it is not appropriate for
backporting. If you need this bug fix in 22.11.6, then a 22.11.x
specific patch is needed for it, that doesn't change the library API.

On Tue, 16 Jul 2024 at 03:44, Du, Frank <frank.du@intel.com> wrote:
>
> Hi Luca,
>
> For this one:
> 97039941b2  Frank Du         net/af_xdp: parse UMEM map info from mempool
>
> It depends on another mempool patch: https://github.com/DPDK/dpdk/commit/2f1015d8d56d32465cc260faf469950ebb9cf73b
>
> I guess it can pass the build if the dependency patch is cherry-picked also.
>
> Thanks,
> Frank
>
> > -----Original Message-----
> > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> > Sent: Monday, July 15, 2024 11:33 PM
> > To: dpdk stable <stable@dpdk.org>
> > Cc: Richardson, Bruce <bruce.richardson@intel.com>; Chaoyong He
> > <chaoyong.he@corigine.com>; Loftus, Ciara <ciara.loftus@intel.com>; Ferruh
> > Yigit <ferruh.yigit@amd.com>; Du, Frank <frank.du@intel.com>; Stokes, Ian
> > <ian.stokes@intel.com>; Keller, Jacob E <jacob.e.keller@intel.com>; Laatz, Kevin
> > <kevin.laatz@intel.com>; Kiran Kumar K <kirankumark@marvell.com>; Long Wu
> > <long.wu@corigine.com>; Morten Brørup <mb@smartsharesystems.com>;
> > Niklas Söderlund <niklas.soderlund@corigine.com>; Nithin Dabilpuram
> > <ndabilpuram@marvell.com>; Stillwell Jr, Paul M
> > <paul.m.stillwell.jr@intel.com>; Peng Zhang <peng.zhang@corigine.com>; Yang,
> > Qiming <qiming.yang@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Rahul
> > Bhansali <rbhansali@marvell.com>; Ray Kinsella <mdr@ashroe.eu>; Satha Rao
> > <skoteshwar@marvell.com>; Satheesh Paul <psatheesh@marvell.com>; Sunil
> > Kumar Kori <skori@marvell.com>; Xiaolong Ye <xiaolong.ye@intel.com>
> > Subject: please help backporting some patches to stable release 22.11.6
> >
> > 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 22.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 22.11 branch, or
> >     - Indicate that the patch should not be backported
> >
> > Please do either of the above by 07/22/24.
> >
> > You can find the a temporary work-in-progress branch of the coming 22.11.6
> > 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 22.11] foo/bar: fix baz
> >
> > With git format-patch, this can be achieved by appending the parameter:
> >     --subject-prefix='PATCH 22.11'
> >
> > Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> >
> > FYI, branch 22.11 is located at tree:
> >    https://git.dpdk.org/dpdk-stable
> >
> > Thanks.
> >
> > Luca Boccassi
> >
> > ---
> > 97039941b2  Frank Du         net/af_xdp: parse UMEM map info from mempool
> > ab1bb0c402  Peng Zhang       net/nfp: add check for numbers of VF representor
> > port
> > fde2a1cb34  Rahul Bhansali   net/cnxk: postpone disabling NPC Rx and MCAM

RE: please help backporting some patches to stable release 22.11.6

[Du, Frank]

Hi,

Ok, so please not backport this XDP commit. It's fine as most XDP PMD user is likely to use the latest version.

Thanks,
Frank

> -----Original Message-----
> From: Luca Boccassi <bluca@debian.org>
> Sent: Tuesday, July 16, 2024 6:30 PM
> To: Du, Frank <frank.du@intel.com>
> Cc: dpdk stable <stable@dpdk.org>
> Subject: Re: please help backporting some patches to stable release 22.11.6
> 
> Hi,
> 
> That mempool patch introduces a new API, so it is not appropriate for
> backporting. If you need this bug fix in 22.11.6, then a 22.11.x specific patch is
> needed for it, that doesn't change the library API.
> 
> On Tue, 16 Jul 2024 at 03:44, Du, Frank <frank.du@intel.com> wrote:
> >
> > Hi Luca,
> >
> > For this one:
> > 97039941b2  Frank Du         net/af_xdp: parse UMEM map info from mempool
> >
> > It depends on another mempool patch:
> >
> https://github.com/DPDK/dpdk/commit/2f1015d8d56d32465cc260faf469950
> ebb
> > 9cf73b
> >
> > I guess it can pass the build if the dependency patch is cherry-picked also.
> >
> > Thanks,
> > Frank
> >
> > > -----Original Message-----
> > > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> > > Sent: Monday, July 15, 2024 11:33 PM
> > > To: dpdk stable <stable@dpdk.org>
> > > Cc: Richardson, Bruce <bruce.richardson@intel.com>; Chaoyong He
> > > <chaoyong.he@corigine.com>; Loftus, Ciara <ciara.loftus@intel.com>;
> > > Ferruh Yigit <ferruh.yigit@amd.com>; Du, Frank <frank.du@intel.com>;
> > > Stokes, Ian <ian.stokes@intel.com>; Keller, Jacob E
> > > <jacob.e.keller@intel.com>; Laatz, Kevin <kevin.laatz@intel.com>;
> > > Kiran Kumar K <kirankumark@marvell.com>; Long Wu
> > > <long.wu@corigine.com>; Morten Brørup <mb@smartsharesystems.com>;
> > > Niklas Söderlund <niklas.soderlund@corigine.com>; Nithin Dabilpuram
> > > <ndabilpuram@marvell.com>; Stillwell Jr, Paul M
> > > <paul.m.stillwell.jr@intel.com>; Peng Zhang
> > > <peng.zhang@corigine.com>; Yang, Qiming <qiming.yang@intel.com>;
> > > Zhang, Qi Z <qi.z.zhang@intel.com>; Rahul Bhansali
> > > <rbhansali@marvell.com>; Ray Kinsella <mdr@ashroe.eu>; Satha Rao
> > > <skoteshwar@marvell.com>; Satheesh Paul <psatheesh@marvell.com>;
> > > Sunil Kumar Kori <skori@marvell.com>; Xiaolong Ye
> > > <xiaolong.ye@intel.com>
> > > Subject: please help backporting some patches to stable release
> > > 22.11.6
> > >
> > > 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 22.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 22.11 branch, or
> > >     - Indicate that the patch should not be backported
> > >
> > > Please do either of the above by 07/22/24.
> > >
> > > You can find the a temporary work-in-progress branch of the coming
> > > 22.11.6 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 22.11] foo/bar: fix baz
> > >
> > > With git format-patch, this can be achieved by appending the parameter:
> > >     --subject-prefix='PATCH 22.11'
> > >
> > > Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> > >
> > > FYI, branch 22.11 is located at tree:
> > >    https://git.dpdk.org/dpdk-stable
> > >
> > > Thanks.
> > >
> > > Luca Boccassi
> > >
> > > ---
> > > 97039941b2  Frank Du         net/af_xdp: parse UMEM map info from
> mempool
> > > ab1bb0c402  Peng Zhang       net/nfp: add check for numbers of VF
> representor
> > > port
> > > fde2a1cb34  Rahul Bhansali   net/cnxk: postpone disabling NPC Rx and
> MCAM

please help backporting some patches to stable release 22.11.6

[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 22.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 22.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 07/31/24.

You can find the a temporary work-in-progress branch of the coming 22.11.6
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 22.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
93db1cfcc3  Stephen Hemminger power: fix number of uncore frequencies

Re: please help backporting some patches to stable release 22.11.6

[Stephen Hemminger]

On Wed, 24 Jul 2024 12:36:14 +0100
luca.boccassi@gmail.com wrote:

> 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 22.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 22.11 branch, or
>     - Indicate that the patch should not be backported
> 
> Please do either of the above by 07/31/24.
> 
> You can find the a temporary work-in-progress branch of the coming 22.11.6
> 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 22.11] foo/bar: fix baz
> 
> With git format-patch, this can be achieved by appending the parameter:
>     --subject-prefix='PATCH 22.11'
> 
> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org".
> 
> FYI, branch 22.11 is located at tree:
>    https://git.dpdk.org/dpdk-stable
> 
> Thanks.
> 
> Luca Boccassi
> 
> ---
> 93db1cfcc3  Stephen Hemminger power: fix number of uncore frequencies

The #define for RTE_MAX_UNCORE_FREQS was introduced in 23.07 by this commit
so backporting directly doesn't make sense, maybe an alternative fix.

Author: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
Date:   Wed Aug 16 03:09:57 2023 -0700

    power: refactor uncore power management API
    
    Currently the uncore power management implementation is vendor specific.
    
    Added new vendor agnostic uncore power interface similar to rte_power
    and rename specific implementations ("rte_power_intel_uncore") to
    "power_intel_uncore" along with functions.
    
    Signed-off-by: Sivaprasad Tummala <sivaprasad.tummala@amd.com>

please help backporting some patches to stable release 22.11.6

[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 22.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 22.11 branch, or
    - Indicate that the patch should not be backported

Please do either of the above by 2024/07/01.

You can find the a temporary work-in-progress branch of the coming 22.11.6
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 22.11] foo/bar: fix baz

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

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

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

Thanks.

Luca Boccassi

---
ecf408d2aa  Bing Zhao        app/testpmd: fix indirect action flush
b9a87346b0  Chengwen Feng    ethdev: fix strict aliasing in link up
0f9ec0cbd2  Kaiwen Deng      net/iavf: fix VF reset when using DCF
590ee5cd95  Nithin Dabilpuram net/cnxk: update SA userdata and keep original cookie
4c2f14bc6d  Sunil Kumar Kori net/cnxk: fix xstats reset