DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Volodymyr Fialko <vfialko@marvell.com>
Cc: dpdk-dev <dev@dpdk.org>,
	Pavan Nikhilesh <pbhagavatula@marvell.com>,
	 Shijith Thotton <sthotton@marvell.com>,
	Jerin Jacob <jerinj@marvell.com>,
	 Anoob Joseph <anoobj@marvell.com>
Subject: Re: [PATCH] event/cnxk: initialize work slot read cache
Date: Tue, 21 Jun 2022 00:32:20 +0530	[thread overview]
Message-ID: <CALBAE1M90RoeuJEEFcjhrqw3L+cph=uF+1BES-OCD0uo8w3kiw@mail.gmail.com> (raw)
In-Reply-To: <20220620112616.3710246-1-vfialko@marvell.com>

On Mon, Jun 20, 2022 at 4:56 PM Volodymyr Fialko <vfialko@marvell.com> wrote:
>
> Initialize gw_rdata with tag type EMPTY. Leaving tag type as
> zero(ATOMIC) may cause some unnecessary head wait, if cache will be used
> before the first update in dequeue/get_work functions.
>
> Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>

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


> ---
>  drivers/event/cnxk/cn10k_eventdev.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/event/cnxk/cn10k_eventdev.c b/drivers/event/cnxk/cn10k_eventdev.c
> index 2f15ff8692..d28eeb3f2f 100644
> --- a/drivers/event/cnxk/cn10k_eventdev.c
> +++ b/drivers/event/cnxk/cn10k_eventdev.c
> @@ -56,6 +56,7 @@ cn10k_sso_init_hws_mem(void *arg, uint8_t port_id)
>         ws->hws_id = port_id;
>         ws->swtag_req = 0;
>         ws->gw_wdata = cn10k_sso_gw_mode_wdata(dev);
> +       ws->gw_rdata = SSO_TT_EMPTY << 32;
>         ws->lmt_base = dev->sso.lmt_base;
>
>         return ws;
> --
> 2.25.1
>

      reply	other threads:[~2022-06-20 19:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20 11:26 Volodymyr Fialko
2022-06-20 19:02 ` 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='CALBAE1M90RoeuJEEFcjhrqw3L+cph=uF+1BES-OCD0uo8w3kiw@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=sthotton@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).