From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
Subject: Re: [PATCH v2 4/6] net/representor: Implement port
 representor PMD
Date: Mon, 11 Dec 2017 15:11:22 +0000
Message-ID: <4d2d74c5-8035-c194-92fd-e52cc65161c5@intel.com>
References: <1510929733-7225-1-git-send-email-mohammad.abdul.awal@intel.com>
 <1510929733-7225-4-git-send-email-mohammad.abdul.awal@intel.com>
 <3098fb7d-02d5-e959-13ae-e9d93cdee0de@intel.com>
 <be133f16-33c8-44ca-9b11-2586ab56fd1e@intel.com>
 <67194c45-6cba-6706-ab63-c9dfbf9eed0c@intel.com>
 <dceea290-91f1-df91-47f9-b57a517f2e34@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Declan Doherty <declan.doherty@intel.com>
To: Remy Horton <remy.horton@intel.com>, Ferruh Yigit
 <ferruh.yigit@intel.com>, dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
Received: from mga17.intel.com (mga17.intel.com [192.55.52.151])
 by dpdk.org (Postfix) with ESMTP id 7C6BF293B
 for <dev@dpdk.org>; Mon, 11 Dec 2017 16:11:26 +0100 (CET)
In-Reply-To: <dceea290-91f1-df91-47f9-b57a517f2e34@intel.com>
Content-Language: en-US
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>



On 11/12/2017 10:08, Remy Horton wrote:
>> int
>> rte_representor_port_register(const char *devargs);
>
> Question is where this *devargs comes from - I don't think there is 
> currently any commandline option to specify a parameter string for PFs.
>
Remy, devargs will be passed by the application who uses the 
rte_representor_port_register API. We are not talking about the EAL args 
here.

> Could go down the zero-conf route of always creating representors for 
> all available VFs, but in that case may as well strip out the parsing 
> code.
>
No zero-conf please. Application should have the control, at least for 
generic cases.