From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <lei.a.yao@intel.com> Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by dpdk.org (Postfix) with ESMTP id F03791B273 for <dev@dpdk.org>; Sat, 29 Sep 2018 04:42:15 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Sep 2018 19:42:14 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,317,1534834800"; d="scan'208";a="90571382" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by fmsmga002.fm.intel.com with ESMTP; 28 Sep 2018 19:42:04 -0700 Received: from fmsmsx122.amr.corp.intel.com (10.18.125.37) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 28 Sep 2018 19:42:04 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by fmsmsx122.amr.corp.intel.com (10.18.125.37) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 28 Sep 2018 19:42:04 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.140]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.27]) with mapi id 14.03.0319.002; Sat, 29 Sep 2018 10:42:02 +0800 From: "Yao, Lei A" <lei.a.yao@intel.com> To: "Hunt, David" <david.hunt@intel.com>, "dev@dpdk.org" <dev@dpdk.org> CC: "Mcnamara, John" <john.mcnamara@intel.com>, "stephen@networkplumber.org" <stephen@networkplumber.org>, "Yao, Lei A" <lei.a.yao@intel.com>, "Burakov, Anatoly" <anatoly.burakov@intel.com> Thread-Topic: [PATCH v5 10/10] doc/vm_power_manager: add JSON interface API info Thread-Index: AQHUVbgEhQrk7mxOI02wXuRh30+xdqUGjhNA Date: Sat, 29 Sep 2018 02:42:01 +0000 Message-ID: <2DBBFF226F7CF64BAFCA79B681719D953A570948@shsmsx102.ccr.corp.intel.com> References: <20180926134037.43606-1-david.hunt@intel.com> <20180926163727.47337-1-david.hunt@intel.com> <20180926163727.47337-11-david.hunt@intel.com> In-Reply-To: <20180926163727.47337-11-david.hunt@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMzUzMzljYWQtMTM1Zi00MTJmLWJhYTktYzY4NDY5NDM2Zjc0IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiU2p5emtnQ0pBNCtReHJ6NVF6MEladzhucEFHQ1FQNlFRQTlLM2FEbkJUQlVMUkRlbndJREY4SjNHWXRLV3hEWiJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v5 10/10] doc/vm_power_manager: add JSON interface API info X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Sat, 29 Sep 2018 02:42:16 -0000 > +:Pair Name: "avg_packet_thresh" > +:Description: Threshold below which the frequency will be set to min for > + the TRAFFIC policy. If the traffic rate is above this and below max, t= he > + frequency will be set to medium. > +:Type: integer > +:Values: The number of packets below which the TRAFFIC policy applies th= e > + minimum frequency, or medium frequency if between avg and max > thresholds. > +:Required: only for TRAFFIC policy > +:Example: > + > + .. code-block:: javascript > + > + "avg_packet_thresh": 100000 Hi, Dave For this traffic policy , seems in previous release, we depends on the=20 application in VM to send the VF mac address info back to the host=20 vm_power_manager sample in host through virtio-serial port.=20 If this JOSN interface is designed for container using VF, do we need add=20 VF mac or ID related info into the TRAFFIC policy JSON file? Otherwise,=20 the host don't know which port to monitor the throughput, I guess.=20