From: David Hunt <david.hunt@intel.com>
To: david.hunt@intel.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 0/3] Core capabilities query
Date: Mon, 30 Sep 2019 14:00:40 +0100 [thread overview]
Message-ID: <20190930130043.2885-1-david.hunt@intel.com> (raw)
In-Reply-To: <20190530161517.11916-2-marcinx.hajkowski@intel.com>
Extend guest channel and sample apps to query CPU capabilities. Useful
when a guest wants to see if there is a high frequency/priority
core available for heavier workloads, i.e. Intel SST-BF.
The guest_cli implements an example of this via the query_cpu_caps cmd.
Please note that these changes depend on
(http://patches.dpdk.org/project/dpdk/list/?series=6568) and
(http://patches.dpdk.org/project/dpdk/list/?series=6585) which
should be applied first.
next prev parent reply other threads:[~2019-09-30 13:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 16:15 [dpdk-dev] [PATCH 0/3] Core capabilities query Hajkowski
2019-05-30 16:15 ` [dpdk-dev] [PATCH 1/3] power: add new packet type for capabilities Hajkowski
2019-09-30 10:55 ` Daly, Lee
2019-09-30 13:00 ` David Hunt [this message]
2019-09-30 13:00 ` [dpdk-dev] [PATCH v2 " David Hunt
2019-09-30 13:00 ` [dpdk-dev] [PATCH v2 2/3] examples/power_manager: send cpu capabilities on vm request David Hunt
2019-09-30 13:00 ` [dpdk-dev] [PATCH v2 3/3] examples/power_guest: send request for specified core capabilities David Hunt
2019-09-30 13:04 ` Hunt, David
2019-10-27 20:16 ` [dpdk-dev] [PATCH v2 0/3] Core capabilities query Thomas Monjalon
2019-05-30 16:15 ` [dpdk-dev] [PATCH 2/3] examples/power_manager: send cpu capabilities on vm request Hajkowski
2019-09-30 10:56 ` Daly, Lee
2019-05-30 16:15 ` [dpdk-dev] [PATCH 3/3] examples/power_guest: send request for specified core capabilities Hajkowski
2019-09-30 10:54 ` Daly, Lee
2019-09-30 12:54 ` Daly, Lee
2019-07-04 19:58 ` [dpdk-dev] [PATCH 0/3] Core capabilities query Thomas Monjalon
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=20190930130043.2885-1-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.