DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Volodymyr Fialko <vfialko@marvell.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH 0/3] fix max pools argument parsing
Date: Fri, 29 Oct 2021 19:48:52 +0530	[thread overview]
Message-ID: <CALBAE1PeBd5Eq0xsxWGV-d8HVRhBEyLgTHgjxSPJ7v5br4g7iQ@mail.gmail.com> (raw)
In-Reply-To: <20211028221446.2455303-1-vfialko@marvell.com>

On Fri, Oct 29, 2021 at 3:45 AM Volodymyr Fialko <vfialko@marvell.com> wrote:
>
> This series should fix issue with max pool argument parsing for cnxk
> platforms
>
> Volodymyr Fialko (3):
>   mempool/cnxk: fix max pools argument parsing
>   common/cnxk: add roc npa init callback support
>   mempool/cnxk: parse max pools during npa initialization


Updated the git log as below[1]

Series Acked-by: Jerin Jacob <jerinj@marvell.com>
Series applied to dpdk-next-net-mrvl/for-next-net. Thanks.

[1]
commit 5a6221d1e943b4e808b88ee2fd457d9ea6da5861 (HEAD -> for-next-net,
origin/for-next-net)
Author: Volodymyr Fialko <vfialko@marvell.com>
Date:   Fri Oct 29 00:14:46 2021 +0200

    mempool/cnxk: postpone devargs parsing

    Use roc_npa_lf_init_cb_register() scheme to register
    callback for max_pools argument parsing.
    This will remove the dependency on the order of PCI
    devices probed.

    Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
    Reviewed-by: Jerin Jacob <jerinj@marvell.com>

commit 2184cde7957e25abf23c8ce12ea3a3f7df4ade70
Author: Volodymyr Fialko <vfialko@marvell.com>
Date:   Fri Oct 29 00:14:45 2021 +0200

    common/cnxk: add ROC NPA init callback support

    Add support for registering callback for ROC NPA init.

    Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
    Reviewed-by: Jerin Jacob <jerinj@marvell.com>

commit b189001ce0ba7c4ccd67b7e40d9ba96cf96b21d1
Author: Volodymyr Fialko <vfialko@marvell.com>
Date:   Fri Oct 29 00:14:44 2021 +0200

    mempool/cnxk: fix max pools argument parsing

    roc_idev_npa_maxpools_set() expects max_pools original value,
    not the AURA.

    Fixes: 0a50a5aad299 ("mempool/cnxk: add device probe/remove")
    Cc: stable@dpdk.org

    Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
    Acked-by: Jerin Jacob <jerinj@marvell.com>


>
>  drivers/common/cnxk/roc_npa.c       | 18 +++++++++++++++++
>  drivers/common/cnxk/roc_npa.h       |  4 ++++
>  drivers/common/cnxk/version.map     |  1 +
>  drivers/mempool/cnxk/cnxk_mempool.c | 31 +++++++++++++++++++----------
>  4 files changed, 44 insertions(+), 10 deletions(-)
>
> --
> 2.25.1
>

      parent reply	other threads:[~2021-10-29 14:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-28 22:14 Volodymyr Fialko
2021-10-28 22:14 ` [dpdk-dev] [PATCH 1/3] mempool/cnxk: " Volodymyr Fialko
2021-10-28 22:14 ` [dpdk-dev] [PATCH 2/3] common/cnxk: add roc npa init callback support Volodymyr Fialko
2021-10-28 22:14 ` [dpdk-dev] [PATCH 3/3] mempool/cnxk: parse max pools during npa initialization Volodymyr Fialko
2021-10-29 14:18 ` Jerin Jacob [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALBAE1PeBd5Eq0xsxWGV-d8HVRhBEyLgTHgjxSPJ7v5br4g7iQ@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerinj@marvell.com \
    --cc=vfialko@marvell.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).