_LWP_MAKECONTEXT(3) BSD Library Functions Manual _LWP_MAKECONTEXT(3)NAME
_lwp_makecontext -- create a new initial light-weight process execution context
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <lwp.h>
void
_lwp_makecontext(ucontext_t *context, void (*start_routine)(void *), void *arg, void *private, caddr_t stack_base, size_t stack_size);
DESCRIPTION
_lwp_makecontext() initializes the context structure pointed to by context in a manner suitable for using with _lwp_create(2). The LWP will
begin execution at the function specified by start_routine which will be passed a single argument arg. The LWP private data pointer will be
set to private. The stack region for the new LWP is specified by the stack_base and stack_size arguments.
The signal mask in the context structure is not initialized by _lwp_makecontext().
SEE ALSO _lwp_create(2), _lwp_getprivate(2)HISTORY
The _lwp_create() system call first appeared in NetBSD 2.0.
BUGS
The LWP private data pointer is not initialized by the current implementation of _lwp_makecontext().
BSD January 16, 2003 BSD
Check Out this Related Man Page
_LWP_PARK(2) BSD System Calls Manual _LWP_PARK(2)NAME
_lwp_park -- wait interruptably in the kernel
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <lwp.h>
int
_lwp_park(const struct timespec *abstime, lwpid_t unpark, const void *hint, const void *unparkhint);
DESCRIPTION
_lwp_park() can be used to synchronize access to resources among multiple light-weight processes. It causes the calling LWP to wait inter-
ruptably in the kernel, until one of the following conditions is met:
o The abstime argument is non-NULL, and the absolute UTC time it specifies has passed.
o The LWP receives a directed signal posted using _lwp_kill(), or is elected to handle a signal on behalf of its containing process.
o The LWP is awoken by another LWP in the same process that has made a call to _lwp_wakeup().
o The LWP is awoken by another LWP in the same process that has made a call to _lwp_unpark() or _lwp_unpark_all().
The preferred method to awaken an LWP sleeping as a result of a call to _lwp_park() is to make a call to _lwp_unpark(), or _lwp_unpark_all().
The _lwp_wakeup() system call is a more general facility, and requires more resources to execute.
The optional hint argument specifies the address of object upon which the LWP is synchronizing. When the hint value is matched between calls
to _lwp_park() and _lwp_unpark() or _lwp_unpark_all(), it may reduce the time necessary for the system to resume execution of waiting LWPs.
The unpark and unparkhint arguments can be used to fold a park operation and unpark operation into a single system call. If unpark is non-
zero, the system will behave as if the following call had been made before the calling thread begins to wait:
_lwp_unpark(unpark, unparkhint);
RETURN VALUES
_lwp_park() may return a value of 0. Otherwise, -1 is returned and errno is set to provide more information.
ERRORS
[EALREADY]
A request was made to wake the LWP before it began to wait in the kernel.
[EINTR] The LWP has been awoken by a signal or by a call to one of the following functions: _lwp_unpark(), _lwp_unpark_all(),
_lwp_wakeup().
[EINVAL] The time value specified by abstime is invalid.
[ESRCH] No LWP can be found in the current process corresponding to unpark.
[ETIMEDOUT]
The UTC time specified by abstime has passed.
SEE ALSO _lwp_unpark(2), _lwp_unpark_all(2), _lwp_wakeup(2)HISTORY
The _lwp_park() system call first appeared in NetBSD 5.0.
BSD September 25, 2007 BSD