Hi kevin,
> -Original Message-
> From: Laatz, Kevin
> Sent: Monday, September 18, 2017 10:54 PM
> To: Yang, Zhiyong ; Matej Vido ;
> Yigit, Ferruh ; dev@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v3 0/4] increase port_id range
>
>
>
> > > -Ori
> > -Original Message-
> > From: Matej Vido [mailto:v...@cesnet.cz]
> > Sent: Wednesday, September 13, 2017 4:14 PM
> > To: Yigit, Ferruh ; Yang, Zhiyong
> > ; dev@dpdk.org
> > Subject: Re: [dpdk-dev] [PATCH v3 0/4] increase port_id range
> >
&
Hi Matej,
> -Original Message-
> From: Matej Vido [mailto:v...@cesnet.cz]
> Sent: Wednesday, September 13, 2017 4:14 PM
> To: Yigit, Ferruh ; Yang, Zhiyong
> ; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v3 0/4] increase port_id range
>
> On 11.09.2017 12:23, Fe
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.
> -Original Message-
> From: Yigit, Ferruh
> Sent: Monday, September 11, 2017 6:23 PM
> To: Yang, Zhiyong ; dev@dpdk.org
> Cc: tho...@monjalon.net; hemant.agra...@nxp.com; Hunt, David
>
> Subject: Re: [PATCH v3 0/4] increase port_id range
>
> On 9/9/2017 3:47 PM, Zhiyong Yang wrote:
> >
On 9/11/2017 11:55 AM, Yang, Zhiyong wrote:
> Hi Ferruh,
>
>> -Original Message-
>> From: Yigit, Ferruh
>> Sent: Monday, September 11, 2017 6:27 PM
>> To: Yang, Zhiyong ; dev@dpdk.org
>> Cc: tho...@monjalon.net; hemant.agra...@nxp.com; Hunt, David
>>
>> Subject: Re: [PATCH v3 0/4] increas
Hi Ferruh,
> -Original Message-
> From: Yigit, Ferruh
> Sent: Monday, September 11, 2017 6:27 PM
> To: Yang, Zhiyong ; dev@dpdk.org
> Cc: tho...@monjalon.net; hemant.agra...@nxp.com; Hunt, David
>
> Subject: Re: [PATCH v3 0/4] increase port_id range
>
> > 3. add 17.11 release note.
> Th
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 relate
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 relate
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.
Dis
10 matches
Mail list logo
