From patchwork Mon May 18 10:39:02 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Sexton, Rory" X-Patchwork-Id: 70378 X-Patchwork-Delegate: thomas@monjalon.net Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id D5048A0093; Mon, 18 May 2020 13:00:17 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 840F11D514; Mon, 18 May 2020 13:00:07 +0200 (CEST) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by dpdk.org (Postfix) with ESMTP id F16111D510 for ; Mon, 18 May 2020 13:00:05 +0200 (CEST) IronPort-SDR: oiLEvIkHXUkxIBE3NrxC3UT9FCz6awNBzZetVu5KI2M+kB4Kes/evRjYywjvzDwFnqL2MF4D+o /+nzVuM9ZKAA== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 May 2020 04:00:05 -0700 IronPort-SDR: tmAEus5Bax5m4Ym5ixN8RsHSE/4J8aRFZx6LIPVHY8Pbw371puqDLWltGMp1R/R41pmoeNx9wk 1PZ5hV3PTl+g== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.73,407,1583222400"; d="scan'208";a="439173143" Received: from silpixa00399913.ir.intel.com (HELO silpixa00399913.ger.corp.intel.com) ([10.237.222.230]) by orsmga005.jf.intel.com with ESMTP; 18 May 2020 04:00:04 -0700 From: "Sexton, Rory" To: dev@dpdk.org, david.hunt@intel.com Cc: "Sexton, Rory" Date: Mon, 18 May 2020 11:39:02 +0100 Message-Id: <20200518103902.27927-3-rory.sexton@intel.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20200518103902.27927-1-rory.sexton@intel.com> References: <20200518103902.27927-1-rory.sexton@intel.com> Subject: [dpdk-dev] [PATCH v2 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" Signed-off-by: Rory Sexton Reviewed-by: David Hunt --- doc/guides/sample_app_ug/vm_power_management.rst | 13 +++++-------- 1 file changed, 5 insertions(+), 8 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..dd0f46158 100644 --- a/doc/guides/sample_app_ug/vm_power_management.rst +++ b/doc/guides/sample_app_ug/vm_power_management.rst @@ -410,20 +410,17 @@ 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 Compiling and Running the Guest Applications --------------------------------------------