.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "CALL_RCU_BH" "9" "09 October 2005" "" ""

.SH NAME
call_rcu_bh \- Queue an RCU for invocation after a quicker grace period.
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void fastcall call_rcu_bh  (struct rcu_head * \fIhead\fB, void (*\fIfunc\fB)
struct rcu_head *rcu);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIhead\fB\fR
structure to be used for queueing the RCU updates.
.TP
\fB\fIfunc\fB\fR
actual update function to be invoked after the grace period
.SH "DESCRIPTION"
.PP
The update function will be invoked some time after a full grace
period elapses, in other words after all currently executing RCU
read-side critical sections have completed. \fBcall_rcu_bh\fR assumes
that the read-side critical sections end on completion of a softirq
handler. This means that read-side critical sections in process
context must not be interrupted by softirqs. This interface is to be
used when most of the read-side critical sections are in softirq context.
RCU read-side critical sections are delimited by \fBrcu_read_lock\fR and
\fBrcu_read_unlock\fR, * if in interrupt context or \fBrcu_read_lock_bh\fR
and \fBrcu_read_unlock_bh\fR, if in process context. These may be nested.