From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Raslan Darawsheh <rasland@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
"leif.y.johansson@ericsson.com" <leif.y.johansson@ericsson.com>
Subject: Re: [dpdk-dev] [PATCH v3] net/mlx5: add power monitoring support
Date: Fri, 30 Apr 2021 13:32:39 +0000 [thread overview]
Message-ID: <DM6PR12MB375360F9B7C3FD7AA1B2E6F3DF5E9@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210429145518.20999-1-akozyrev@nvidia.com>
> -----Original Message-----
> From: Alexander Kozyrev <akozyrev@nvidia.com>
> Sent: Thursday, April 29, 2021 17:55
> To: dev@dpdk.org
> Cc: Raslan Darawsheh <rasland@nvidia.com>; Matan Azrad
> <matan@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>;
> leif.y.johansson@ericsson.com
> Subject: [PATCH v3] net/mlx5: add power monitoring support
>
> Support the PMD power management API in MLX5 driver.
> The monitor policy of this API puts a CPU core to sleep until a data in some
> monitored memory address is changed by the NIC.
> Implement the get_monitor_addr function to return an address of a CQE
> owner bit to monitor the arrival of a new packet.
>
> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
next prev parent reply other threads:[~2021-04-30 13:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 15:32 [dpdk-dev] [PATCH] " Alexander Kozyrev
2021-04-08 3:25 ` [dpdk-dev] [PATCH v2] " Alexander Kozyrev
2021-04-29 14:55 ` [dpdk-dev] [PATCH v3] " Alexander Kozyrev
2021-04-30 13:32 ` Slava Ovsiienko [this message]
2021-05-03 10:57 ` Raslan Darawsheh
2021-05-04 17:40 ` Ferruh Yigit
2021-05-04 17:43 ` Thomas Monjalon
2021-05-05 11:57 ` Burakov, Anatoly
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=DM6PR12MB375360F9B7C3FD7AA1B2E6F3DF5E9@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=akozyrev@nvidia.com \
--cc=dev@dpdk.org \
--cc=leif.y.johansson@ericsson.com \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.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).