'\" t
.\"     Title: __wake_up
.\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\"      Date: May 2018
.\"    Manual: Driver Basics
.\"    Source: Kernel Hackers Manual 3.16.56
.\"  Language: English
.\"
.TH "__WAKE_UP" "9" "May 2018" "Kernel Hackers Manual 3\&.16\&" "Driver Basics"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
__wake_up \- wake up threads blocked on a waitqueue\&.
.SH "SYNOPSIS"
.HP \w'void\ __wake_up('u
.BI "void __wake_up(wait_queue_head_t\ *\ " "q" ", unsigned\ int\ " "mode" ", int\ " "nr_exclusive" ", void\ *\ " "key" ");"
.SH "ARGUMENTS"
.PP
\fIq\fR
.RS 4
the waitqueue
.RE
.PP
\fImode\fR
.RS 4
which threads
.RE
.PP
\fInr_exclusive\fR
.RS 4
how many wake\-one or wake\-many threads to wake up
.RE
.PP
\fIkey\fR
.RS 4
is directly passed to the wakeup function
.RE
.SH "DESCRIPTION"
.PP
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\&.
.SH "COPYRIGHT"
.br