From: Thomas Monjalon <thomas@monjalon.net>
To: David Hunt <david.hunt@intel.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: rasland@nvidia.com, matan@nvidia.com, viacheslavo@nvidia.com,
leif.y.johansson@ericsson.com,
Alexander Kozyrev <akozyrev@nvidia.com>,
dev@dpdk.org, Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [dpdk-dev] [PATCH v3] net/mlx5: add power monitoring support
Date: Tue, 04 May 2021 19:43:49 +0200 [thread overview]
Message-ID: <2178881.vkImXlHJGI@thomas> (raw)
In-Reply-To: <58e9e3da-4b88-877c-934c-6b57387b3440@intel.com>
04/05/2021 19:40, Ferruh Yigit:
> On 4/29/2021 3:55 PM, Alexander Kozyrev wrote:
> > 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>
>
> Hi David, Anatoly,
>
> What to you think adding "Power Monitoring" as a new feature in the NIC feature
> table? So the drivers supporting it can advertise it.
> https://doc.dpdk.org/guides/nics/overview.html
>
> For it need to,
> - add "Power Monitoring" to template .ini file,
> '.doc/guides/nics/features/default.ini'
> - Document it in the features file, '.doc/guides/nics/features.rst'
> - Update driver .ini files to advertise the feature, like 'ixgbe.ini'
+1
next prev parent reply other threads:[~2021-05-04 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 15:32 [dpdk-dev] [PATCH] net/mlx5: add power monitoring support 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
2021-05-03 10:57 ` Raslan Darawsheh
2021-05-04 17:40 ` Ferruh Yigit
2021-05-04 17:43 ` Thomas Monjalon [this message]
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=2178881.vkImXlHJGI@thomas \
--to=thomas@monjalon.net \
--cc=akozyrev@nvidia.com \
--cc=anatoly.burakov@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=leif.y.johansson@ericsson.com \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=viacheslavo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.