All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hunt <david.hunt@intel.com>
To: dev@dpdk.org
Cc: david.hunt@intel.com
Subject: [dpdk-dev] [PATCH v1 3/3] lib/power: clarify comment on priority core
Date: Thu,  2 May 2019 12:18:15 +0100	[thread overview]
Message-ID: <20190502111815.29343-3-david.hunt@intel.com> (raw)
In-Reply-To: <20190502111815.29343-1-david.hunt@intel.com>

As part of the documentation update on the changes made to the power
library for 19.05, information on SST-BF was added. This patch updates
the comment to clarify that a priority core is an SST-BF high
frequency core.

Signed-off-by: David Hunt <david.hunt@intel.com>
---
 lib/librte_power/rte_power.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/librte_power/rte_power.h b/lib/librte_power/rte_power.h
index 0650112ad..01f88588b 100644
--- a/lib/librte_power/rte_power.h
+++ b/lib/librte_power/rte_power.h
@@ -259,7 +259,7 @@ struct rte_power_core_capabilities {
 		RTE_STD_C11
 		struct {
 			uint64_t turbo:1;	/**< Turbo can be enabled. */
-			uint64_t priority:1;	/**< Priority core */
+			uint64_t priority:1;	/**< SST-BF high freq core */
 		};
 	};
 };
-- 
2.17.1


  parent reply	other threads:[~2019-05-02 11:19 UTC|newest]

Thread overview: 7+ 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 ` [dpdk-dev] [PATCH v1 2/3] doc: add release note for power changes David Hunt
2019-05-02 15:55   ` Mcnamara, John
2019-05-03 20:17     ` Thomas Monjalon
2019-05-02 11:18 ` David Hunt [this message]
2019-05-02 16:14   ` [dpdk-dev] [PATCH v1 3/3] lib/power: clarify comment on priority core Mcnamara, John
2019-05-02 15:53 ` [dpdk-dev] [PATCH v1 1/3] doc/distributor: add SST-BF enhancement info 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=20190502111815.29343-3-david.hunt@intel.com \
    --to=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    /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.