From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Hunt, David" <david.hunt@intel.com>
Subject: Re: [PATCH v5 07/10] examples/power: add json string
	handling
Date: Mon, 1 Oct 2018 12:03:27 +0100
Message-ID: <80ea5e45-e2a8-1d86-a7ed-9d8589f375ed@intel.com>
References: <20180926134037.43606-1-david.hunt@intel.com>
 <20180926163727.47337-1-david.hunt@intel.com>
 <20180926163727.47337-8-david.hunt@intel.com>
 <2DBBFF226F7CF64BAFCA79B681719D953A570DDE@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" <john.mcnamara@intel.com>,
 "stephen@networkplumber.org" <stephen@networkplumber.org>,
 "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "Yao, Lei A" <lei.a.yao@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Return-path: <dev-bounces@dpdk.org>
Received: from mga05.intel.com (mga05.intel.com [192.55.52.43])
 by dpdk.org (Postfix) with ESMTP id 9B4C0569B
 for <dev@dpdk.org>; Mon,  1 Oct 2018 13:03:30 +0200 (CEST)
In-Reply-To: <2DBBFF226F7CF64BAFCA79B681719D953A570DDE@shsmsx102.ccr.corp.intel.com>
Content-Language: en-US
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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Hi Lei,


On 30/9/2018 2:54 AM, Yao, Lei A wrote:
>> +#ifdef USE_JANSSON
>> +static int
>> +parse_json_to_pkt(json_t *element, struct channel_packet *pkt)
>> +{
>> +	const char *key;
>> +	json_t *value;
>> +	int ret;
>> +
>> +	memset(pkt, 0, sizeof(struct channel_packet));
>> +
>> +	pkt->nb_mac_to_monitor = 0;
>> +	pkt->t_boost_status.tbEnabled = false;
>> +	pkt->workload = LOW;
>> +	pkt->policy_to_use = TIME;
>> +	pkt->command = PKT_POLICY;
>> +	pkt->core_type = CORE_TYPE_PHYSICAL;
>> +
>
> Hi, Dave
>
> For the workload policy ,  it's set to LOW by default,
> but we can't change it again using JSON file channel. Is it
> by design?

It was because the VMs currently only send binary structures. But they
may send JSON data in the future so I should add it now.
I'll upload a new version of the patch set today.

Thanks,
Dave.