PTHREAD_B...ETPSHARED(3P)

πŸ’… PTHREAD_B...ETPSHARED(3P) β€” get & set the process-shared attribute of the barrier attributes object πŸ’…

okay bestie, welcome to the POSIX Programmer's Manual, section 3P. This page is literally called pthread_barrierattr_getpshared / pthread_barrierattr_setpshared (yeah the title's truncated, the manual does that, it's giving drama). Pull up a chair, we're talking barriers. πŸ¦‹


✨ PROLOG ✨

Real talk: this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (so go check the corresponding Linux manual page for the actual Linux tea β˜•), or the interface might not even be implemented on Linux at all. Not every system shows up to the party. πŸ’€


🌸 NAME 🌸

pthread_barrierattr_getpshared, pthread_barrierattr_setpshared β€” get and set the process-shared attribute of the barrier attributes object. Periodt.


πŸŽ€ SYNOPSIS πŸŽ€

#include <pthread.h>

int pthread_barrierattr_getpshared(const pthread_barrierattr_t
    *restrict attr, int *restrict pshared);
int pthread_barrierattr_setpshared(pthread_barrierattr_t *attr,
    int pshared);

πŸ’– DESCRIPTION πŸ’–

So here's the vibe:

  • pthread_barrierattr_getpshared() shall obtain the value of the process-shared attribute from the attributes object referenced by attr.
  • pthread_barrierattr_setpshared() shall set the process-shared attribute in an initialized attributes object referenced by attr.

Now, the process-shared attribute gets set to PTHREAD_PROCESS_SHARED to permit a barrier to be operated upon by any thread that has access to the memory where the barrier is allocated. (See Section 2.9.9, Synchronization Object Copies and Alternative Mappings for the extra requirements, iykyk.) The default value of the attribute shall be PTHREAD_PROCESS_PRIVATE. Both constants, PTHREAD_PROCESS_SHARED and PTHREAD_PROCESS_PRIVATE, are defined in <pthread.h>.

Additional attributes, their default values, and the names of the associated functions to get and set those attribute values are implementation-defined. So like, your implementation's business, not ours. πŸ™ˆ

⚠️ The behavior is undefined if the value specified by the attr argument to pthread_barrierattr_getpshared() or pthread_barrierattr_setpshared() does not refer to an initialized barrier attributes object. Like, don't do that. Not cute.

⭐ RETURN VALUE ⭐

  • If successful, pthread_barrierattr_getpshared() shall return zero and store the value of the process-shared attribute of attr into the object referenced by the pshared parameter. Otherwise, an error number shall be returned to indicate the error.
  • If successful, pthread_barrierattr_setpshared() shall return zero; otherwise, an error number shall be returned to indicate the error.

πŸ”₯ ERRORS πŸ”₯

The pthread_barrierattr_setpshared() function may fail if:

  • EINVAL β€” The new value specified for the process-shared attribute is not one of the legal values PTHREAD_PROCESS_SHARED or PTHREAD_PROCESS_PRIVATE. Bestie, pick a real one. 😭

Also: these functions shall not return an error code of [EINTR]. Nope, never, not today.

The following sections are informative. πŸ‘‘


🌈 EXAMPLES 🌈

None.

(Yeah. That's the whole section. Iconic minimalism honestly. ✨)


🧚 APPLICATION USAGE 🧚

The pthread_barrierattr_getpshared() and pthread_barrierattr_setpshared() functions are part of the Thread Process-Shared Synchronization option and need not be provided on all implementations. So if they're missing on your system, it's not you, it's them. πŸ’œ


πŸ‘‘ RATIONALE πŸ‘‘

If an implementation detects that the value specified by the attr argument to pthread_barrierattr_getpshared() or pthread_barrierattr_setpshared() does not refer to an initialized barrier attributes object, it is recommended that the function should fail and report an [EINVAL] error. Just a lil recommendation, as a treat. 🫢


πŸ“ FUTURE DIRECTIONS πŸ“

None.


πŸ’œ SEE ALSO πŸ’œ

  • pthread_barrier_destroy()
  • pthread_barrierattr_destroy()

The Base Definitions volume of POSIX.1‐2017, <pthread.h>


Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group.

In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html.


okay that's the whole page bestie, you ate it πŸ’… this lil masterpiece came from IEEE/The Open Group, 2017 β€” and that's the official PTHREAD_B...ETPSHARED(3P) footer energy, folded in like a lil bow πŸŽ€ mwah, go set some attributes, no cap βœ¨πŸ¦‹

πŸ“¦ where this page comes from