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 v5] event/cnxk: use WFE LDP loop for getwork routine
Date: Fri, 1 Mar 2024 17:42:16 +0530	[thread overview]
Message-ID: <CALBAE1OFkoPgB8S7V-6j4dzHst-WHXsVEYAqZ2YoR81cufsyUw@mail.gmail.com> (raw)
In-Reply-To: <20240227081153.20826-1-pbhagavatula@marvell.com>

On Tue, Feb 27, 2024 at 1:42 PM <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
> 'RTE_ARM_USE_WFE' enabled.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>

1) Changed subject as "event/cnxk: support power-saving during dequeue
operation"
2) Applied following diff
for-main]dell[dpdk-next-eventdev] $ git diff
diff --git a/doc/guides/rel_notes/release_24_03.rst
b/doc/guides/rel_notes/release_24_03.rst
index 7e68b697c2..080815c000 100644
--- a/doc/guides/rel_notes/release_24_03.rst
+++ b/doc/guides/rel_notes/release_24_03.rst
@@ -140,8 +140,7 @@ New Features

 * **Updated Marvell cnxk eventdev driver.**

-  * Added ARM WFE instruction in ``GETWORK(rte_event_dev_dequeue)`` routine
-    to save power while waiting for SSO to schedule work.
+  * Added power-saving functionality during polling within the
``rte_event_dequeue_burst()`` API.


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

      reply	other threads:[~2024-03-01 12:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27  8:11 pbhagavatula
2024-03-01 12:12 ` 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=CALBAE1OFkoPgB8S7V-6j4dzHst-WHXsVEYAqZ2YoR81cufsyUw@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).