From: "Hunt, David" <david.hunt@intel.com>
To: Reshma Pattan <reshma.pattan@intel.com>, <dev@dpdk.org>
Subject: Re: [PATCH] doc: add removal note for power empty poll API
Date: Tue, 30 Aug 2022 10:23:09 +0100 [thread overview]
Message-ID: <0ff66a20-749d-1770-6eb4-471515890238@intel.com> (raw)
In-Reply-To: <20220802152206.1210365-1-reshma.pattan@intel.com>
On 02/08/2022 16:22, Reshma Pattan wrote:
> Add removal note for experimental empty poll API.
>
> CC: David Hunt <david.hunt@intel.com>
>
> Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
> ---
> doc/guides/prog_guide/power_man.rst | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/doc/guides/prog_guide/power_man.rst b/doc/guides/prog_guide/power_man.rst
> index 98cfd3c1f3..2e47d87cbb 100644
> --- a/doc/guides/prog_guide/power_man.rst
> +++ b/doc/guides/prog_guide/power_man.rst
> @@ -192,6 +192,12 @@ User Cases
> ----------
> The mechanism can applied to any device which is based on polling. e.g. NIC, FPGA.
>
> +Removal Note
> +------------
> +The experimental empty poll APIs will be removed from the library in a future DPDK release.
> +Suggest to use new lcore poll busyness APIs added in 22.11.
> +
> +
> Ethernet PMD Power Management API
> ---------------------------------
>
Hi Reshma,
Yes, these APIs will be superseded by the newer poll busyness telemetry.
Acked-by: David Hunt <david.hunt@intel.com>
next prev parent reply other threads:[~2022-08-30 9:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 15:22 Reshma Pattan
2022-08-30 9:23 ` Hunt, David [this message]
2022-10-05 8:44 ` [PATCH v2] " Reshma Pattan
2022-10-05 12:27 ` Thomas Monjalon
2022-10-07 13:54 ` Pattan, Reshma
2022-10-07 13:40 ` [PATCH v3] " Reshma Pattan
2022-10-31 15:26 ` Thomas Monjalon
2022-11-02 12:35 ` Pattan, Reshma
2022-11-02 12:31 ` [PATCH v4] doc: add removal warning " Reshma Pattan
2022-11-02 12:41 ` [PATCH v5] " Reshma Pattan
2022-11-15 15:35 ` Thomas Monjalon
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=0ff66a20-749d-1770-6eb4-471515890238@intel.com \
--to=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=reshma.pattan@intel.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).