Re: [dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment

2018-12-21 Thread Ferruh Yigit
t; Sent: Wednesday, July 20, 2016 8:12 AM >>> To: Tootoonchian, Amin >>> Cc: dev at dpdk.org; Kerlin, MarcinX >>> Subject: Re: [dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment >>> >>> Hi, >>> >>> 2016-07-20 15:

Re: [dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment

2017-09-04 Thread Sergio Gonzalez Monroy
t dpdk.org; Kerlin, MarcinX Subject: Re: [dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment Hi, 2016-07-20 15:07, Tootoonchian, Amin: Thomas, your thoughts? I have 2 thoughts: - it is too big for 16.07 - it is related to multi-process mechanism, maintained by Sergio ;) Sorry I won

[dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment

2016-08-24 Thread Tootoonchian, Amin
ev] [PATCH] ethdev: ensure consistent port id assignment > > Hi, > > 2016-07-20 15:07, Tootoonchian, Amin: > > Thomas, your thoughts? > > I have 2 thoughts: > - it is too big for 16.07 > - it is related to multi-process mechanism, maintained by Sergio ;) > > Sorry I won't look at it shortly.

[dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment

2016-07-22 Thread Tootoonchian, Amin
Inline: > > This is the intended behavior with this patch. Ports are to be created > > only by the primary process. This is required for correct operation > > IMO, because if we allow secondary processes to create ports > > dynamically (and locally use conflicting port ids) without any > > synchro

[dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment

2016-07-21 Thread Kerlin, MarcinX
t port id assignment > > > > Hi Amin, > > > > > -Original Message- > > > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Tootoonchian, > > > Amin > > > Sent: Tuesday, July 12, 2016 4:01 AM > > > To: thomas.monjalon at 6win

[dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment

2016-07-20 Thread Tootoonchian, Amin
> -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Wednesday, July 20, 2016 8:12 AM > To: Tootoonchian, Amin > Cc: dev at dpdk.org; Kerlin, MarcinX > Subject: Re: [dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment >

[dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment

2016-07-20 Thread Thomas Monjalon
Hi, 2016-07-20 15:07, Tootoonchian, Amin: > Thomas, your thoughts? I have 2 thoughts: - it is too big for 16.07 - it is related to multi-process mechanism, maintained by Sergio ;) Sorry I won't look at it shortly.

[dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment

2016-07-20 Thread Tootoonchian, Amin
nment > > Hi Amin, > > > -Original Message- > > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Tootoonchian, > > Amin > > Sent: Tuesday, July 12, 2016 4:01 AM > > To: thomas.monjalon at 6wind.com > > Cc: dev at dpdk.org > > Subject: [dpdk-dev]

[dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment

2016-07-20 Thread Kerlin, MarcinX
Hi Amin, > -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Tootoonchian, Amin > Sent: Tuesday, July 12, 2016 4:01 AM > To: thomas.monjalon at 6wind.com > Cc: dev at dpdk.org > Subject: [dpdk-dev] [PATCH] ethdev: ensure consistent port id a

[dpdk-dev] [PATCH] ethdev: ensure consistent port id assignment

2016-07-12 Thread Tootoonchian, Amin
The rte_eth_dev_allocate() code has an implicit assumption that the port id assignment in the secondary process is consistent with that of the primary. The current code breaks if the enumeration of ethdevs in primary and secondary processes are not identical (e.g., when the black/whitelist and vdev