From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 239E8A0540; Tue, 14 Jul 2020 18:02:35 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id BB1A21D409; Tue, 14 Jul 2020 18:02:21 +0200 (CEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 7357E1D166 for ; Tue, 14 Jul 2020 18:02:17 +0200 (CEST) IronPort-SDR: MM2wpKFVHEYY/T+16Qvb3JgBJuqHi9RWGWhHbfTT1FTUMirvmCfBiBDViUDeYAZsP8Hy86HSVe aSYug+/XZ9bg== X-IronPort-AV: E=McAfee;i="6000,8403,9681"; a="146446392" X-IronPort-AV: E=Sophos;i="5.75,350,1589266800"; d="scan'208";a="146446392" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Jul 2020 09:02:03 -0700 IronPort-SDR: mfrDlVYVu7fgqFyzc/3WntC23cZYgP8O6iyy2Mn/osVksXrPqepLr17DX/LirqRbHR3eJU70gJ Mn9jwpp8PpnA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,350,1589266800"; d="scan'208";a="285799828" Received: from silpixa00399913.ir.intel.com ([10.237.213.189]) by orsmga006.jf.intel.com with ESMTP; 14 Jul 2020 09:02:03 -0700 From: Rory Sexton To: dev@dpdk.org, david.hunt@intel.com Date: Tue, 14 Jul 2020 17:02:00 +0100 Message-Id: <20200714160200.1727417-3-rory.sexton@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20200714160200.1727417-1-rory.sexton@intel.com> References: <20200714160200.1727417-1-rory.sexton@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [v4 3/3] doc: update vm_power_manager cmdline options in doc X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Updating the vm_power_manager docs to reflect changes made in previous patches in set. Signed-off-by: Rory Sexton Reviewed-by: David Hunt --- v4: no changes --- doc/guides/sample_app_ug/vm_power_management.rst | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/doc/guides/sample_app_ug/vm_power_management.rst b/doc/guides/sample_app_ug/vm_power_management.rst index e98277ccb..1b6de8e93 100644 --- a/doc/guides/sample_app_ug/vm_power_management.rst +++ b/doc/guides/sample_app_ug/vm_power_management.rst @@ -410,19 +410,21 @@ There are a couple of command line parameters for enabling the out-of-band monitoring of branch ratios on cores doing busy polling using PMDs as described below: -``--core-list {list of cores}`` +``--core-branch-ratio {list of cores}:{branch ratio for listed cores}`` Specify the list of cores to monitor the ratio of branch misses to branch hits. A tightly-polling PMD thread has a very low branch ratio, therefore the core frequency scales down to the minimum allowed value. On receiving packets, the code path changes, causing the branch ratio to increase. When the ratio goes above the ratio threshold, the core frequency scales up to the maximum - allowed value. - -``--branch-ratio {ratio}`` - Specify a floating-point number that identifies the threshold at which - to scale up or down for the given workload. The default branch ratio - is 0.01 and needs adjustment for different workloads. + allowed value. The specified branch-ratio is a floating point number + that identifies the threshold at which to scale up or down for the + elements of the core-list. If not included the default branch ratio of + 0.01 but will need adjustment for different workloads + + This parameter can be used multiple times for different sets of cores. + The branch ratio mechanism can also be useful for non-PMD cores and + hyper-threaded environments where C-States are disabled. Compiling and Running the Guest Applications -- 2.25.1