Re: Thread name support
On 16/01/17 12:56, Chris Johns wrote: Who looks at the RTEMS documentation to figure out what a POSIX function >does? I never used the POSIX API manual. > Many people do. It is important when something is not working as expected. Not all users are keen to jump into the RTEMS source code to figure something out, or have an inside to outside view. I use The Open Group web site to figure out what a POSIX API function is supposed to do. From my point of view there is little sense in duplicating this information. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Thread name support
On 16/1/17 7:19 pm, Sebastian Huber wrote: > > > On 16/01/17 09:08, Chris Johns wrote: >> On 16/1/17 5:52 pm, Sebastian Huber wrote: >>> On 13/01/17 18:59, Gedare Bloom wrote: On Fri, Jan 13, 2017 at 3:25 AM, Sebastian Huber wrote: > Hello, > > I added optional user-defined thread names. > > https://devel.rtems.org/ticket/2858 > > The GNU pthread extensions pthread_getname_np() and > pthread_setname_np() are > now available in RTEMS and work for all threads (internal, Classic, > POSIX, > FreeBSD). > > http://man7.org/linux/man-pages/man3/pthread_setname_np.3.html > > The maximum thread name size is a configuration option > (CONFIGURE_MAXIMUM_THREAD_NAME_SIZE). > > Where should this new feature be documented in the C user manual? > I guess at posix-users/thread.rst? I don't know if we have a list of function calls that work across the APIs, but I know quite a few do. >>> It think the POSIX API manual should be replaced by a simple list of >>> POSIX functions implemented by RTEMS. Each with a link to The Open Group >>> documentation and optionally RTEMS-specific things. >> What happens with PDF or epub format? Currently the PDF documentation is >> fully contained. Doing this means the users has to have internet access >> to use it. > > Who looks at the RTEMS documentation to figure out what a POSIX function > does? I never used the POSIX API manual. > Many people do. It is important when something is not working as expected. Not all users are keen to jump into the RTEMS source code to figure something out, or have an inside to outside view. >> >>> The thread names are available for every API. It should be documented >>> somewhere in the user manual. >>> >> The C user manual? The RTEMS User Manual does not contain any API >> related doco. > > Hm, the C user manual and the RTEMS User Manual are different things? > Yes. The RTEMS User manual is about using RTEMS, the ecosystem, setting up a development environment, the type of host hardware you need, debugging, applications, support, tools and more. The C User manual is the detail on runtime configuration, the Classic API and other C base interfaces users need to call to run RTEMS. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Thread name support
On 16/01/17 09:08, Chris Johns wrote: On 16/1/17 5:52 pm, Sebastian Huber wrote: On 13/01/17 18:59, Gedare Bloom wrote: On Fri, Jan 13, 2017 at 3:25 AM, Sebastian Huber wrote: Hello, I added optional user-defined thread names. https://devel.rtems.org/ticket/2858 The GNU pthread extensions pthread_getname_np() and pthread_setname_np() are now available in RTEMS and work for all threads (internal, Classic, POSIX, FreeBSD). http://man7.org/linux/man-pages/man3/pthread_setname_np.3.html The maximum thread name size is a configuration option (CONFIGURE_MAXIMUM_THREAD_NAME_SIZE). Where should this new feature be documented in the C user manual? I guess at posix-users/thread.rst? I don't know if we have a list of function calls that work across the APIs, but I know quite a few do. It think the POSIX API manual should be replaced by a simple list of POSIX functions implemented by RTEMS. Each with a link to The Open Group documentation and optionally RTEMS-specific things. What happens with PDF or epub format? Currently the PDF documentation is fully contained. Doing this means the users has to have internet access to use it. Who looks at the RTEMS documentation to figure out what a POSIX function does? I never used the POSIX API manual. The thread names are available for every API. It should be documented somewhere in the user manual. The C user manual? The RTEMS User Manual does not contain any API related doco. Hm, the C user manual and the RTEMS User Manual are different things? -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Thread name support
On 16/1/17 5:52 pm, Sebastian Huber wrote: > On 13/01/17 18:59, Gedare Bloom wrote: >> On Fri, Jan 13, 2017 at 3:25 AM, Sebastian Huber >> wrote: >>> Hello, >>> >>> I added optional user-defined thread names. >>> >>> https://devel.rtems.org/ticket/2858 >>> >>> The GNU pthread extensions pthread_getname_np() and >>> pthread_setname_np() are >>> now available in RTEMS and work for all threads (internal, Classic, >>> POSIX, >>> FreeBSD). >>> >>> http://man7.org/linux/man-pages/man3/pthread_setname_np.3.html >>> >>> The maximum thread name size is a configuration option >>> (CONFIGURE_MAXIMUM_THREAD_NAME_SIZE). >>> >>> Where should this new feature be documented in the C user manual? >>> >> I guess at posix-users/thread.rst? I don't know if we have a list of >> function calls that work across the APIs, but I know quite a few do. > > It think the POSIX API manual should be replaced by a simple list of > POSIX functions implemented by RTEMS. Each with a link to The Open Group > documentation and optionally RTEMS-specific things. What happens with PDF or epub format? Currently the PDF documentation is fully contained. Doing this means the users has to have internet access to use it. > > The thread names are available for every API. It should be documented > somewhere in the user manual. > The C user manual? The RTEMS User Manual does not contain any API related doco. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Thread name support
On 13/01/17 18:59, Gedare Bloom wrote: On Fri, Jan 13, 2017 at 3:25 AM, Sebastian Huber wrote: Hello, I added optional user-defined thread names. https://devel.rtems.org/ticket/2858 The GNU pthread extensions pthread_getname_np() and pthread_setname_np() are now available in RTEMS and work for all threads (internal, Classic, POSIX, FreeBSD). http://man7.org/linux/man-pages/man3/pthread_setname_np.3.html The maximum thread name size is a configuration option (CONFIGURE_MAXIMUM_THREAD_NAME_SIZE). Where should this new feature be documented in the C user manual? I guess at posix-users/thread.rst? I don't know if we have a list of function calls that work across the APIs, but I know quite a few do. It think the POSIX API manual should be replaced by a simple list of POSIX functions implemented by RTEMS. Each with a link to The Open Group documentation and optionally RTEMS-specific things. The thread names are available for every API. It should be documented somewhere in the user manual. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Thread name support
On Fri, Jan 13, 2017 at 3:25 AM, Sebastian Huber wrote: > Hello, > > I added optional user-defined thread names. > > https://devel.rtems.org/ticket/2858 > > The GNU pthread extensions pthread_getname_np() and pthread_setname_np() are > now available in RTEMS and work for all threads (internal, Classic, POSIX, > FreeBSD). > > http://man7.org/linux/man-pages/man3/pthread_setname_np.3.html > > The maximum thread name size is a configuration option > (CONFIGURE_MAXIMUM_THREAD_NAME_SIZE). > > Where should this new feature be documented in the C user manual? > I guess at posix-users/thread.rst? I don't know if we have a list of function calls that work across the APIs, but I know quite a few do. > -- > Sebastian Huber, embedded brains GmbH > > Address : Dornierstr. 4, D-82178 Puchheim, Germany > Phone : +49 89 189 47 41-16 > Fax : +49 89 189 47 41-09 > E-Mail : sebastian.hu...@embedded-brains.de > PGP : Public key available on request. > > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. > > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Thread name support
Hello, I added optional user-defined thread names. https://devel.rtems.org/ticket/2858 The GNU pthread extensions pthread_getname_np() and pthread_setname_np() are now available in RTEMS and work for all threads (internal, Classic, POSIX, FreeBSD). http://man7.org/linux/man-pages/man3/pthread_setname_np.3.html The maximum thread name size is a configuration option (CONFIGURE_MAXIMUM_THREAD_NAME_SIZE). Where should this new feature be documented in the C user manual? -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
