From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ferruh.yigit@intel.com>
Received: from mga07.intel.com (mga07.intel.com [134.134.136.100])
 by dpdk.org (Postfix) with ESMTP id 6692C6D45
 for <dev@dpdk.org>; Mon, 11 Sep 2017 12:26:47 +0200 (CEST)
Received: from fmsmga003.fm.intel.com ([10.253.24.29])
 by orsmga105.jf.intel.com with ESMTP; 11 Sep 2017 03:26:47 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.42,377,1500966000"; d="scan'208";a="899066023"
Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.57])
 ([10.237.220.57])
 by FMSMGA003.fm.intel.com with ESMTP; 11 Sep 2017 03:26:44 -0700
To: Zhiyong Yang <zhiyong.yang@intel.com>, dev@dpdk.org
Cc: thomas@monjalon.net, hemant.agrawal@nxp.com, david.hunt@intel.com
References: <20170904055734.21354-1-zhiyong.yang@intel.com>
 <20170909144727.46388-1-zhiyong.yang@intel.com>
From: Ferruh Yigit <ferruh.yigit@intel.com>
Message-ID: <951fd16f-2f2f-e079-fcd3-d5cddef1ba7d@intel.com>
Date: Mon, 11 Sep 2017 11:26:44 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <20170909144727.46388-1-zhiyong.yang@intel.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [dpdk-dev] [PATCH v3 0/4] increase port_id range
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
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>
X-List-Received-Date: Mon, 11 Sep 2017 10:26:48 -0000

On 9/9/2017 3:47 PM, Zhiyong Yang wrote:
> port_id is currently defined as uint8_t, which is limited to the range
> 0 to 255. A larger range is required for vdev scalability.
> 
> It is necessary for a redefinition of port_id to extend it from
> 1 bytes to 2 bytes. All ethdev APIs and usages related to port_id will
> be changed at the same time.
> 
> Discussion about port_id is the following thread.
> http://www.dpdk.org/dev/patchwork/patch/23208/
> 
> Changes in V2:
> 1. cover more PMDs to increase port_id range.
> 2. cover more examples to increase port_id range.
> 3. add 17.11 release note.
> 
> Changes in V3:
> 1.  cover mlx4 and mlx5.
> 2.  add to increase port_id range in test code.
> 3.  The patch "librte_mbuf: modify port initialization value" is merged
> into the patchset.
> 
> Zhiyong Yang (4):
>   ethdev: increase port_id range
>   test: increase port_id range
>   examples: increase port_id range
>   librte_mbuf: modify port initialization value

This breaks almost all rte_eth_dev APIs, and will effect almost all
users! So please document this update in release notes.

Thanks,
ferruh