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 v4] event/cnxk: use WFE LDP loop for getwork routine
Date: Sun, 25 Feb 2024 20:50:42 +0530	[thread overview]
Message-ID: <CALBAE1NMsre4ugd-bWmzGsnA-ts=T0mx8PrjjOWbNxfAB1PHBA@mail.gmail.com> (raw)
In-Reply-To: <20240201220311.7215-1-pbhagavatula@marvell.com>

On Fri, Feb 2, 2024 at 5:59 AM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Use WFE LDP loop while polling for GETWORK completion for better
> power savings.

> Disabled by default and can be enabled by configuring meson with
> -Dc_args='-DRTE_ARM_USE_WFE'.

Since this section is not yet merged. We can remove this commit log.

>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> ---
>  v4 Changes:
>  - Split patches
>
>  doc/guides/eventdevs/cnxk.rst     |  9 ++++++

Please update the release notes for this PMD feature.


>  drivers/event/cnxk/cn10k_worker.h | 52 +++++++++++++++++++++++++------
>  2 files changed, 52 insertions(+), 9 deletions(-)
>
> diff --git a/doc/guides/eventdevs/cnxk.rst b/doc/guides/eventdevs/cnxk.rst
> index cccb8a0304..04f5b5025b 100644
> --- a/doc/guides/eventdevs/cnxk.rst
> +++ b/doc/guides/eventdevs/cnxk.rst
> @@ -198,6 +198,15 @@ Runtime Config Options
>
>      -a 0002:0e:00.0,tim_eclk_freq=122880000-1000000000-0
>
> +Power Savings on CN10K
> +----------------------
> +
> +ARM cores can additionally use WFE when polling for transactions on SSO bus
> +to save power i.e., in the event dequeue call ARM core can enter WFE and exit
> +when either work has been scheduled or dequeue timeout has reached.
> +This can be enabled by configuring meson with the following option
> +``-Dc_args='-DRTE_ARM_USE_WFE'``.

The last section can be made as generic, as other patches are not merged.
i.e This can be enabled by selecting RTE_ARM_USE_WFE or so.

      reply	other threads:[~2024-02-25 15:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 19:36 [PATCH] " pbhagavatula
2024-01-09  7:56 ` Jerin Jacob
2024-01-17 14:25 ` [PATCH v2 1/2] config/arm: allow WFE to be enabled config time pbhagavatula
2024-01-17 14:26   ` [PATCH v2 2/2] event/cnxk: use WFE LDP loop for getwork routine pbhagavatula
2024-01-18  1:52   ` [PATCH v2 1/2] config/arm: allow WFE to be enabled config time Ruifeng Wang
2024-01-21 15:21   ` [PATCH v3 " pbhagavatula
2024-01-21 15:21     ` [PATCH v3 2/2] event/cnxk: use WFE LDP loop for getwork routine pbhagavatula
2024-01-22  6:37     ` [PATCH v3 1/2] config/arm: allow WFE to be enabled config time fengchengwen
2024-01-22  6:43     ` Ruifeng Wang
2024-02-01 16:37       ` Jerin Jacob
2024-02-01 22:03     ` [PATCH v4] event/cnxk: use WFE LDP loop for getwork routine pbhagavatula
2024-02-25 15:20       ` 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='CALBAE1NMsre4ugd-bWmzGsnA-ts=T0mx8PrjjOWbNxfAB1PHBA@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).