Re: help with pthread_t deprecation / api changes

2022-12-13 Thread Tyler Retzlaff
On Tue, Dec 13, 2022 at 09:39:24PM +0100, Morten Brørup wrote: > > From: Thomas Monjalon [mailto:tho...@monjalon.net] > > Sent: Tuesday, 13 December 2022 20.34 > > > > 13/12/2022 18:38, Tyler Retzlaff: > > > Okay, just one final confirmation. This is what we would like? > > > > > > * completely re

RE: help with pthread_t deprecation / api changes

2022-12-13 Thread Morten Brørup
> From: Thomas Monjalon [mailto:tho...@monjalon.net] > Sent: Tuesday, 13 December 2022 20.34 > > 13/12/2022 18:38, Tyler Retzlaff: > > Okay, just one final confirmation. This is what we would like? > > > > * completely remove the existing rte_thread_getname api. > > - by implication this means

Re: help with pthread_t deprecation / api changes

2022-12-13 Thread Thomas Monjalon
13/12/2022 18:38, Tyler Retzlaff: > On Tue, Dec 13, 2022 at 09:32:06AM +0100, Thomas Monjalon wrote: > > 12/12/2022 18:45, Tyler Retzlaff: > > > On Sun, Dec 11, 2022 at 08:50:48AM +0100, Thomas Monjalon wrote: > > > > 10/12/2022 00:49, Tyler Retzlaff: > > > > > On Fri, Dec 09, 2022 at 10:13:44PM +0

Re: help with pthread_t deprecation / api changes

2022-12-13 Thread Tyler Retzlaff
On Tue, Dec 13, 2022 at 09:32:06AM +0100, Thomas Monjalon wrote: > 12/12/2022 18:45, Tyler Retzlaff: > > On Sun, Dec 11, 2022 at 08:50:48AM +0100, Thomas Monjalon wrote: > > > 10/12/2022 00:49, Tyler Retzlaff: > > > > On Fri, Dec 09, 2022 at 10:13:44PM +0100, Thomas Monjalon wrote: > > > > > 09/12/

Re: help with pthread_t deprecation / api changes

2022-12-13 Thread Thomas Monjalon
12/12/2022 18:45, Tyler Retzlaff: > On Sun, Dec 11, 2022 at 08:50:48AM +0100, Thomas Monjalon wrote: > > 10/12/2022 00:49, Tyler Retzlaff: > > > On Fri, Dec 09, 2022 at 10:13:44PM +0100, Thomas Monjalon wrote: > > > > 09/12/2022 21:06, Tyler Retzlaff: > > > > > On Fri, Dec 09, 2022 at 08:48:14AM -0

Re: help with pthread_t deprecation / api changes

2022-12-12 Thread Tyler Retzlaff
On Sun, Dec 11, 2022 at 08:50:48AM +0100, Thomas Monjalon wrote: > 10/12/2022 00:49, Tyler Retzlaff: > > On Fri, Dec 09, 2022 at 10:13:44PM +0100, Thomas Monjalon wrote: > > > 09/12/2022 21:06, Tyler Retzlaff: > > > > On Fri, Dec 09, 2022 at 08:48:14AM -0800, Stephen Hemminger wrote: > > > > > On F

Re: help with pthread_t deprecation / api changes

2022-12-10 Thread Thomas Monjalon
10/12/2022 00:49, Tyler Retzlaff: > On Fri, Dec 09, 2022 at 10:13:44PM +0100, Thomas Monjalon wrote: > > 09/12/2022 21:06, Tyler Retzlaff: > > > On Fri, Dec 09, 2022 at 08:48:14AM -0800, Stephen Hemminger wrote: > > > > On Fri, 09 Dec 2022 08:53:57 +0100 > > > > Thomas Monjalon wrote: > > > > > >

Re: help with pthread_t deprecation / api changes

2022-12-09 Thread Tyler Retzlaff
On Fri, Dec 09, 2022 at 02:38:49PM -0800, Stephen Hemminger wrote: > On Fri, 09 Dec 2022 22:14:33 +0100 > Thomas Monjalon wrote: > > > 09/12/2022 17:48, Stephen Hemminger: > > > On Fri, 09 Dec 2022 08:53:57 +0100 > > > Thomas Monjalon wrote: > > > > > > > > > If some execution environment doe

Re: help with pthread_t deprecation / api changes

2022-12-09 Thread Tyler Retzlaff
On Fri, Dec 09, 2022 at 10:13:44PM +0100, Thomas Monjalon wrote: > 09/12/2022 21:06, Tyler Retzlaff: > > On Fri, Dec 09, 2022 at 08:48:14AM -0800, Stephen Hemminger wrote: > > > On Fri, 09 Dec 2022 08:53:57 +0100 > > > Thomas Monjalon wrote: > > > > > > > > > If some execution environment doesn't

Re: help with pthread_t deprecation / api changes

2022-12-09 Thread Stephen Hemminger
On Fri, 09 Dec 2022 22:14:33 +0100 Thomas Monjalon wrote: > 09/12/2022 17:48, Stephen Hemminger: > > On Fri, 09 Dec 2022 08:53:57 +0100 > > Thomas Monjalon wrote: > > > > > > > If some execution environment doesn't support thread names, it could > > > > > return a string that makes it possib

Re: help with pthread_t deprecation / api changes

2022-12-09 Thread Thomas Monjalon
09/12/2022 17:48, Stephen Hemminger: > On Fri, 09 Dec 2022 08:53:57 +0100 > Thomas Monjalon wrote: > > > > > If some execution environment doesn't support thread names, it could > > > > return a string that makes it possible for a human to identify the > > > > thread, e.g. the tread id. Again,

Re: help with pthread_t deprecation / api changes

2022-12-09 Thread Thomas Monjalon
09/12/2022 21:06, Tyler Retzlaff: > On Fri, Dec 09, 2022 at 08:48:14AM -0800, Stephen Hemminger wrote: > > On Fri, 09 Dec 2022 08:53:57 +0100 > > Thomas Monjalon wrote: > > > > > > > If some execution environment doesn't support thread names, it could > > > > > return a string that makes it poss

Re: help with pthread_t deprecation / api changes

2022-12-09 Thread Tyler Retzlaff
hey, combining the reply to both Thomas and Stephen since i think this series http://mails.dpdk.org/archives/dev/2022-December/257238.html addresses both feedback comments. On Fri, Dec 09, 2022 at 08:48:14AM -0800, Stephen Hemminger wrote: > On Fri, 09 Dec 2022 08:53:57 +0100 > Thomas Monjalon w

Re: help with pthread_t deprecation / api changes

2022-12-09 Thread Stephen Hemminger
On Fri, 09 Dec 2022 08:53:57 +0100 Thomas Monjalon wrote: > > > If some execution environment doesn't support thread names, it could > > > return a string that makes it possible for a human to identify the > > > thread, e.g. the tread id. Again, this is assuming that it is only used > > > for

Re: help with pthread_t deprecation / api changes

2022-12-08 Thread Thomas Monjalon
02/12/2022 20:57, Tyler Retzlaff: > On Fri, Dec 02, 2022 at 09:03:25AM +0100, Morten Brørup wrote: > > +Bruce, FreeBSD EAL maintainer > > > > > > > > This is one of the consequences of a bloated EAL. > > > > How is an application supposed to run on top of an EAL that isn't fully > > implemente

Re: help with pthread_t deprecation / api changes

2022-12-02 Thread Tyler Retzlaff
On Fri, Dec 02, 2022 at 09:03:25AM +0100, Morten Brørup wrote: > +Bruce, FreeBSD EAL maintainer > > > > This is one of the consequences of a bloated EAL. > > How is an application supposed to run on top of an EAL that isn't fully > implemented by the underlying environments? yep, i'm aware of

RE: help with pthread_t deprecation / api changes

2022-12-02 Thread Morten Brørup
+Bruce, FreeBSD EAL maintainer > From: Tyler Retzlaff [mailto:roret...@linux.microsoft.com] > Sent: Friday, 2 December 2022 02.12 > > On Wed, Nov 30, 2022 at 02:54:27PM -0800, Tyler Retzlaff wrote: > > hi folks, > > > > i'd like to continue work moving to our platform abstracted > rte_thread > >

Re: help with pthread_t deprecation / api changes

2022-12-01 Thread Tyler Retzlaff
On Wed, Nov 30, 2022 at 02:54:27PM -0800, Tyler Retzlaff wrote: > hi folks, > > i'd like to continue work moving to our platform abstracted rte_thread > but ran into a hiccup. for some recent and not so recent apis it appears > they managed to slip in without ever being __experimental. > > as a

help with pthread_t deprecation / api changes

2022-11-30 Thread Tyler Retzlaff
hi folks, i'd like to continue work moving to our platform abstracted rte_thread but ran into a hiccup. for some recent and not so recent apis it appears they managed to slip in without ever being __experimental. as a function of the dpdk project api/abi policy this means we can't change or remo