DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: David Hunt <david.hunt@intel.com>,
	Anatoly Burakov <anatoly.burakov@intel.com>
Cc: rasland@nvidia.com, matan@nvidia.com, viacheslavo@nvidia.com,
	Alexander Kozyrev <akozyrev@nvidia.com>,
	dev@dpdk.org, Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v3] net/mlx5: add power monitoring support
Date: Tue, 4 May 2021 18:40:30 +0100
Message-ID: <58e9e3da-4b88-877c-934c-6b57387b3440@intel.com> (raw)
In-Reply-To: <20210429145518.20999-1-akozyrev@nvidia.com>

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.

For it need to,
- add "Power Monitoring" to template .ini file,
- Document it in the features file, '.doc/guides/nics/features.rst'
- Update driver .ini files to advertise the feature, like 'ixgbe.ini'

  parent reply	other threads:[~2021-05-04 17:40 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
2021-05-03 10:57     ` Raslan Darawsheh
2021-05-04 17:40     ` Ferruh Yigit [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58e9e3da-4b88-877c-934c-6b57387b3440@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=akozyrev@nvidia.com \
    --cc=anatoly.burakov@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=leif.y.johansson@ericsson.com \
    --cc=matan@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git