From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Hunt, David" Subject: Re: [PATCH v5 10/10] doc/vm_power_manager: add JSON interface API info Date: Mon, 1 Oct 2018 12:02:03 +0100 Message-ID: <3e00f906-756c-a6f8-2bcf-09c9226609fc@intel.com> References: <20180926134037.43606-1-david.hunt@intel.com> <20180926163727.47337-1-david.hunt@intel.com> <20180926163727.47337-11-david.hunt@intel.com> <2DBBFF226F7CF64BAFCA79B681719D953A570948@shsmsx102.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "Mcnamara, John" , "stephen@networkplumber.org" , "Burakov, Anatoly" To: "Yao, Lei A" , "dev@dpdk.org" Return-path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 74914569B for ; Mon, 1 Oct 2018 13:02:08 +0200 (CEST) In-Reply-To: <2DBBFF226F7CF64BAFCA79B681719D953A570948@shsmsx102.ccr.corp.intel.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Lei, On 29/9/2018 3:42 AM, Yao, Lei A wrote: >> +: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, the >> + frequency will be set to medium. >> +:Type: integer >> +:Values: The number of packets below which the TRAFFIC policy applies the >> + 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 > application in VM to send the VF mac address info back to the host > vm_power_manager sample in host through virtio-serial port. > If this JOSN interface is designed for container using VF, do we need add > VF mac or ID related info into the TRAFFIC policy JSON file? Otherwise, > the host don't know which port to monitor the throughput, I guess. > > Well spotted. I'll add this and upload a new version. Thanks, Dave.