From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from office2.cesnet.cz (office2.cesnet.cz [195.113.144.244]) by dpdk.org (Postfix) with ESMTP id E76367CB6 for ; Wed, 13 Sep 2017 10:14:26 +0200 (CEST) Received: from [IPv6:2001:67c:1220:80c:f8f4:f055:211e:fe80] (unknown [IPv6:2001:67c:1220:80c:f8f4:f055:211e:fe80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by office2.cesnet.cz (Postfix) with ESMTPSA id 6AFF6400275; Wed, 13 Sep 2017 10:14:26 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cesnet.cz; s=office2; t=1505290466; bh=9fNYnbGGlix7mKfqthriyuwyNgOwjy3unogRob7hZTE=; h=Subject:To:References:From:Date:In-Reply-To; b=Y8vaFdhmn0ZlfYPrnyH6adTapdwYrQEB+BAQUzuFYAY/5LDIQDpFl94fIrnEssrid mWeQ/vkJQ2rJgqYI9eGLqq4wUZPKE8jy+b+f/TuAiCTvUqQdMRFgdADD7ys8idavgY bZ0ORnk5ygZAkLF5drcV5ezJNH3dbh9GKnc9jiRE= To: Ferruh Yigit , Zhiyong Yang , dev@dpdk.org References: <20170904055734.21354-1-zhiyong.yang@intel.com> <20170909144727.46388-1-zhiyong.yang@intel.com> <4a6842e5-18f7-9f1d-0ccc-3c904f1f95f4@intel.com> From: Matej Vido Message-ID: <741f79a3-7107-d2bc-29b8-d91e5d26a925@cesnet.cz> Date: Wed, 13 Sep 2017 10:14:26 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <4a6842e5-18f7-9f1d-0ccc-3c904f1f95f4@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Sep 2017 08:14:27 -0000 On 11.09.2017 12:23, Ferruh Yigit wrote: > 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 >> > PMD Maintainers, please review this patch for your PMD, this innocent > uint8_t to uint16_t change may break your PMD! Regarding the szedata2 PMD this change is fine. Thanks, Matej