DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
	"Hunt, David" <david.hunt@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] net/iavf: implement power management API
Date: Thu, 25 Mar 2021 07:53:30 +0000	[thread overview]
Message-ID: <05122b3c93bf42b78862130753a7adba@intel.com> (raw)
In-Reply-To: <3b43d8f4-baf1-8735-2381-cf19ed184581@intel.com>



> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Burakov, Anatoly
> Sent: Thursday, March 11, 2021 9:37 PM
> To: Hunt, David <david.hunt@intel.com>; dev@dpdk.org
> Cc: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v1] net/iavf: implement power management
> API
> 
> On 11-Mar-21 11:55 AM, David Hunt wrote:
> > Implement support for the power management API by implementing a
> > `get_monitor_addr` function that will return an address of an RX
> > ring's status bit.
> >
> > This patch is basically a cut-and-paste of the changes already
> > committed in ixgbe, i40e and ice drivers in 21.02. This extends the
> > availability of the power-saving mechanism to the iavf driver, which
> > is needed for those use-cases using virtual functions.
> >
> > Patch set where PMD Power Manamgement added in 21.02:
> > http://patchwork.dpdk.org/project/dpdk/list/?series=14756
> >
> > Signed-off-by: David Hunt <david.hunt@intel.com>
> > ---
> 
> LGTM as far as using the API correctly goes.
> 
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>

Applied to dpdk-next-net-intel.

Thanks
Qi


  reply	other threads:[~2021-03-25  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 11:55 David Hunt
2021-03-11 13:37 ` Burakov, Anatoly
2021-03-25  7:53   ` Zhang, Qi Z [this message]
2021-03-31 12:27   ` Ferruh Yigit

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=05122b3c93bf42b78862130753a7adba@intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@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).