DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Srujana Challa <schalla@marvell.com>
Cc: pbhagavatula@marvell.com, sthotton@marvell.com,
	rbhansali@marvell.com,  jerinj@marvell.com, dev@dpdk.org,
	ndabilpuram@marvell.com
Subject: Re: [PATCH] event/cnxk: add wmb after steorl for event mode
Date: Tue, 30 May 2023 15:30:13 +0530	[thread overview]
Message-ID: <CALBAE1Oej+WSfkMsZ9PEGObEv=z49eWo7tS3371-P_tCwj-BTg@mail.gmail.com> (raw)
In-Reply-To: <20230530094208.3438943-1-schalla@marvell.com>

On Tue, May 30, 2023 at 3:12 PM Srujana Challa <schalla@marvell.com> wrote:
>
> From: Author Srujana Challa <schalla@marvell.com>
>
> LMTST area can be overwritten before read by HW between to consecutive
> steorl operations. Hence, add wmb() after steorl op to make sure
> the lmtst operation is complete.

lmtst -> LMTST

Change the subject to "fix ...."
And add Fixes: tag


>
> Signed-off-by: Srujana Challa <schalla@marvell.com>
> ---
>  drivers/event/cnxk/cn10k_tx_worker.h | 8 +++-----
>  1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/event/cnxk/cn10k_tx_worker.h b/drivers/event/cnxk/cn10k_tx_worker.h
> index c18786a14c..81fe31c4b9 100644
> --- a/drivers/event/cnxk/cn10k_tx_worker.h
> +++ b/drivers/event/cnxk/cn10k_tx_worker.h
> @@ -43,7 +43,6 @@ cn10k_sso_tx_one(struct cn10k_sso_hws *ws, struct rte_mbuf *m, uint64_t *cmd,
>                  const uint64_t *txq_data, const uint32_t flags)
>  {
>         uint8_t lnum = 0, loff = 0, shft = 0;
> -       uint16_t ref_cnt = m->refcnt;
>         struct cn10k_eth_txq *txq;
>         uintptr_t laddr;
>         uint16_t segdw;
> @@ -98,10 +97,9 @@ cn10k_sso_tx_one(struct cn10k_sso_hws *ws, struct rte_mbuf *m, uint64_t *cmd,
>
>         roc_lmt_submit_steorl(lmt_id, pa);
>
> -       if (flags & NIX_TX_OFFLOAD_MBUF_NOFF_F) {
> -               if (ref_cnt > 1)
> -                       rte_io_wmb();
> -       }
> +       /* Memory barrier to make sure lmtst store completes */
> +       rte_io_wmb();
> +
>         return 1;
>  }
>
> --
> 2.25.1
>

  reply	other threads:[~2023-05-30 10:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30  9:42 Srujana Challa
2023-05-30 10:00 ` Jerin Jacob [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-30 11:53 Srujana Challa
2023-05-30  9:39 Srujana Challa

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='CALBAE1Oej+WSfkMsZ9PEGObEv=z49eWo7tS3371-P_tCwj-BTg@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=rbhansali@marvell.com \
    --cc=schalla@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).