DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ray Kinsella <mdr@ashroe.eu>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: jerinj@marvell.com, Nithin Dabilpuram <ndabilpuram@marvell.com>,
	"Kiran Kumar K" <kirankumark@marvell.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	Satha Rao <skoteshwar@marvell.com>,
	Shijith Thotton <sthotton@marvell.com>,
	dev@dpdk.org
Subject: Re: [PATCH] event/cnxk: add SLMTST support to Tx adapter
Date: Wed, 27 Apr 2022 05:00:11 -0400	[thread overview]
Message-ID: <877d7anbok.fsf@mdr78.vserver.site> (raw)
In-Reply-To: <20220427070624.9258-1-pbhagavatula@marvell.com>


Pavan Nikhilesh <pbhagavatula@marvell.com> writes:

> Scheduled LMTST uses in-core LSW (LMTST scheduling widget) to
> coordinate with SSO and send a LMTST to the destination
> coprocessor without the need for the core to be the head of
> the scheduling context it is currently holding.
>
> Use SLMTST to send mbuf to NIX-TX for transmit. SLMTST only
> supports transmitting a single WQE.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> ---
>  Depends-on: Series-22634
>
>  drivers/common/cnxk/hw/ssow.h        |  7 +++++++
>  drivers/common/cnxk/roc_dev_priv.h   |  6 ++++++
>  drivers/common/cnxk/roc_io.h         |  8 ++++++++
>  drivers/common/cnxk/roc_io_generic.h |  7 +++++++
>  drivers/common/cnxk/roc_nix.c        | 19 +++++++++++++++++++
>  drivers/common/cnxk/roc_nix.h        |  4 ++++
>  drivers/common/cnxk/roc_sso.c        | 23 +++++++++++++++++++++++
>  drivers/common/cnxk/roc_sso.h        |  2 ++
>  drivers/common/cnxk/version.map      |  2 ++
>  drivers/event/cnxk/cn10k_eventdev.c  | 11 +++++++++++
>  drivers/event/cnxk/cn10k_worker.h    | 19 +++++++++++++------
>  drivers/event/cnxk/cnxk_eventdev.h   |  2 +-
>  12 files changed, 103 insertions(+), 7 deletions(-)
>
Acked-by: Ray Kinsella <mdr@ashroe.eu>

-- 
Regards, Ray K

      reply	other threads:[~2022-04-27  9:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27  7:06 Pavan Nikhilesh
2022-04-27  9:00 ` Ray Kinsella [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=877d7anbok.fsf@mdr78.vserver.site \
    --to=mdr@ashroe.eu \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@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).