From: Thomas Monjalon <thomas@monjalon.net>
To: "Hunt, David" <david.hunt@intel.com>
Cc: dev@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1 2/3] doc: add release note for power changes
Date: Fri, 03 May 2019 22:17:29 +0200 [thread overview]
Message-ID: <6327666.Stf6abXUKs@xps> (raw)
Message-ID: <20190503201729.LiuNLMbiFI7EuJS4RBfR7Xq9LjdJzArENlnn6N5qdu8@z> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23F60BF85@IRSMSX103.ger.corp.intel.com>
02/05/2019 17:55, Mcnamara, John:
> From: David Hunt
> > In the Power Library, a new bit has been added to the mask returned by
> > rte_power_get_capabilities which indicates whether the core is an Intel
> > SST-BF high frequency core.
> >
> > The Distributor sample app has also been enhanced to make use of SST-BF
> > cores, and pin relevant workloads to the higher frequency cores, if
> > available in the core mask provided to the application.
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
Applied. Please try to update the release notes at the same time
as the code. Thanks
next prev parent reply other threads:[~2019-05-03 20:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 11:18 [dpdk-dev] [PATCH v1 1/3] doc/distributor: add SST-BF enhancement info David Hunt
2019-05-02 11:18 ` David Hunt
2019-05-02 11:18 ` [dpdk-dev] [PATCH v1 2/3] doc: add release note for power changes David Hunt
2019-05-02 11:18 ` David Hunt
2019-05-02 15:55 ` Mcnamara, John
2019-05-02 15:55 ` Mcnamara, John
2019-05-03 20:17 ` Thomas Monjalon [this message]
2019-05-03 20:17 ` Thomas Monjalon
2019-05-02 11:18 ` [dpdk-dev] [PATCH v1 3/3] lib/power: clarify comment on priority core David Hunt
2019-05-02 11:18 ` David Hunt
2019-05-02 16:14 ` Mcnamara, John
2019-05-02 16:14 ` Mcnamara, John
2019-05-02 15:53 ` [dpdk-dev] [PATCH v1 1/3] doc/distributor: add SST-BF enhancement info Mcnamara, John
2019-05-02 15:53 ` Mcnamara, John
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=6327666.Stf6abXUKs@xps \
--to=thomas@monjalon.net \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).