DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: pbhagavatula@marvell.com
Cc: jerinj@marvell.com, Shijith Thotton <sthotton@marvell.com>, dev@dpdk.org
Subject: Re: [PATCH] event/cnxk: fix missing mempool cookie marking
Date: Mon, 7 Nov 2022 22:56:08 +0530	[thread overview]
Message-ID: <CALBAE1OC__EQ-4-H4ZV8TwxtFBG_g9a-CC04P7gF7Vj0TWQvjw@mail.gmail.com> (raw)
In-Reply-To: <20221103161631.3851-1-pbhagavatula@marvell.com>

On Thu, Nov 3, 2022 at 9:46 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Mark chunks mempool objects as "put" as they are freed to NPA
> automatically when they are parsed by TIM HW.
>
> Fixes: 300b796262a1 ("event/cnxk: add timer arm routine")
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>

Applied to dpdk-next-net-eventdev/for-main. Thanks


> ---
>  drivers/event/cnxk/cnxk_tim_worker.h | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/event/cnxk/cnxk_tim_worker.h b/drivers/event/cnxk/cnxk_tim_worker.h
> index 8d8ed1d3a1..eda84c6f31 100644
> --- a/drivers/event/cnxk/cnxk_tim_worker.h
> +++ b/drivers/event/cnxk/cnxk_tim_worker.h
> @@ -217,6 +217,7 @@ cnxk_tim_insert_chunk(struct cnxk_tim_bkt *const bkt,
>         if (unlikely(rte_mempool_get(tim_ring->chunk_pool, (void **)&chunk)))
>                 return NULL;
>
> +       RTE_MEMPOOL_CHECK_COOKIES(tim_ring->chunk_pool, (void **)&chunk, 1, 0);
>         *(uint64_t *)(chunk + tim_ring->nb_chunk_slots) = 0;
>         if (bkt->nb_entry) {
>                 *(uint64_t *)(((struct cnxk_tim_ent *)(uintptr_t)
> --
> 2.25.1
>

      reply	other threads:[~2022-11-07 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 16:16 pbhagavatula
2022-11-07 17:26 ` 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=CALBAE1OC__EQ-4-H4ZV8TwxtFBG_g9a-CC04P7gF7Vj0TWQvjw@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=sthotton@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).