Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

__wake_up(9) [suse man page]

__WAKE_UP(9)							   Driver Basics						      __WAKE_UP(9)

NAME
__wake_up - wake up threads blocked on a waitqueue. SYNOPSIS
void __wake_up(wait_queue_head_t * q, unsigned int mode, int nr_exclusive, void * key); ARGUMENTS
q the waitqueue mode which threads nr_exclusive how many wake-one or wake-many threads to wake up key is directly passed to the wakeup function DESCRIPTION
It may be assumed that this function implies a write memory barrier before changing the task state if and only if any tasks are woken up. COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 __WAKE_UP(9)

Check Out this Related Man Page

sem_post(2)							System Calls Manual						       sem_post(2)

NAME
sem_post - unlock a POSIX semaphore SYNOPSIS
DESCRIPTION
is used to post the semaphore referenced by sem. The calling thread will not return from its call to unless it can either: increment the semaphore value, if there are no blocked threads on this semaphore; give the semaphore to a blocked thread, if there are any blocked threads on this semaphore; or have an error condition. If the semaphore value is < 0, the semaphore has blocked threads, waiting for it to become available (the absolute value of the semaphore's value indicates the number of waiters at that moment). If the semaphore value is >= 0, the semaphore has no waiters. If the semaphore has no waiters at the time its value is checked, the semaphore's value will be atomically incremented, with respect to the checking of its value, up to its maximum value as specified by If the semaphore has waiters at the time its value is checked, the semaphore value is not changed. Instead, the calling thread will attempt to wake up a waiter. If the semaphore has waiters having realtime priori- ties, the thread must wake up the highest priority waiter. Otherwise the thread at the head of the channel queue is woken up. When a waiter is successfully woken, the semaphore being posted will be given to the woken waiter. In other words, the state of the sema- phore remains unchanged. Instead, the semaphore being posted will be inherited by the waiter being woken from this call to If the specified semaphore referred to by sem is a named semaphore, then this semaphore must have been opened by the calling process with The calling process must have both read and write permissions on the semaphore to perform this operation. The routine may be called asyn- chronously, i.e. from a signal handler. To use this function, link in the realtime library by specifying on the compiler or linker command line. EXAMPLES
The following call to will post the semaphore sem. RETURN VALUE
A successful call to will return 0 and the calling thread would have posted the semaphore. Otherwise, the call to will return -1 with errno set to the appropriate value of the error condition. ERRORS
fails and does not perform the requested operation if any of the following conditions are encountered: [EPERM] The calling process does not have the privileges necessary to post the semaphore. [EINVAL] The argument sem does not refer to a valid semaphore. SEE ALSO
<semaphore.h>. STANDARDS CONFORMANCE
sem_post(2)
Man Page

3 More Discussions You Might Find Interesting

1. Programming

how to wake up a thread that blocking at epoll_wait?

I have two threads: one maintains a thread-safe message queue (handle this queue at the beginning of every loop) and deals with tcp connections, the other one posts message to the former one. the problem is, while the former one was blocking at epoll_wait, it's not sure that how long until the... (0 Replies)
Discussion started by: cometeor
0 Replies

2. UNIX for Advanced & Expert Users

how to wake up a thread that blocking at epoll_wait?

(0 Replies)
Discussion started by: cometeor
0 Replies

3. UNIX for Dummies Questions & Answers

Linux Device Driver: how can an ISR wake up a user-thread?

Hi all, Is it possible to do the following in Linux (kernel 2.6.x): - A user-space thread goes to "sleep". Using any call/mechanism - On a hardware generated interrupt, the Interrupt handler (ISR) "wakes" the sleeping user-thread. I have seen wait_event() and wake_up() but it appears... (1 Reply)
Discussion started by: agaurav
1 Replies