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: add preliminary Tx queue depth check
Date: Wed, 14 Sep 2022 18:28:37 +0530 [thread overview]
Message-ID: <CALBAE1M+XCDExcLiBCpJzYo0A9XC30QoWr8E-4yZrKtL3B9gSw@mail.gmail.com> (raw)
In-Reply-To: <20220816153545.7536-1-pbhagavatula@marvell.com>
On Tue, Aug 16, 2022 at 9:05 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> add preliminary Tx queue depth check and return on failure.
> Once the check passes, tx_adapter_enqueue() function becomes
> a blocking call till it succeeds.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Applied to dpdk-next-net-eventdev/for-main. Thanks
> ---
> drivers/event/cnxk/cn10k_worker.h | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/event/cnxk/cn10k_worker.h b/drivers/event/cnxk/cn10k_worker.h
> index 0915f404e0..a71e076ff8 100644
> --- a/drivers/event/cnxk/cn10k_worker.h
> +++ b/drivers/event/cnxk/cn10k_worker.h
> @@ -655,6 +655,11 @@ cn10k_sso_hws_event_tx(struct cn10k_sso_hws *ws, struct rte_event *ev,
> }
>
> m = ev->mbuf;
> + txq = cn10k_sso_hws_xtract_meta(m, txq_data);
> + if (((txq->nb_sqb_bufs_adj -
> + __atomic_load_n((int16_t *)txq->fc_mem, __ATOMIC_RELAXED))
> + << txq->sqes_per_sqb_log2) <= 0)
> + return 0;
> cn10k_sso_tx_one(ws, m, cmd, lmt_id, lmt_addr, ev->sched_type, txq_data,
> flags);
>
> --
> 2.25.1
>
prev parent reply other threads:[~2022-09-14 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 15:35 pbhagavatula
2022-09-14 12:58 ` 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=CALBAE1M+XCDExcLiBCpJzYo0A9XC30QoWr8E-4yZrKtL3B9gSw@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).