From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 7C6BF293B for ; Mon, 11 Dec 2017 16:11:26 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Dec 2017 07:11:25 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,392,1508828400"; d="scan'208";a="1551345" Received: from awalabdu-mobl.ger.corp.intel.com (HELO [10.252.21.64]) ([10.252.21.64]) by fmsmga007.fm.intel.com with ESMTP; 11 Dec 2017 07:11:23 -0800 To: Remy Horton , Ferruh Yigit , dev@dpdk.org Cc: Declan Doherty 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> <67194c45-6cba-6706-ab63-c9dfbf9eed0c@intel.com> From: Mohammad Abdul Awal Message-ID: <4d2d74c5-8035-c194-92fd-e52cc65161c5@intel.com> Date: Mon, 11 Dec 2017 15:11:22 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Subject: Re: [dpdk-dev] [PATCH v2 4/6] net/representor: Implement port representor PMD 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: , X-List-Received-Date: Mon, 11 Dec 2017 15:11:26 -0000 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.