.\" 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 "BALANCE_DIRTY_PAGES_RATELIMITED" "" "06 October 2005" "" ""

.SH NAME
balance_dirty_pages_ratelimited \- balance dirty memory state
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void balance_dirty_pages_ratelimited  (struct address_space * \fImapping\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fImapping\fB\fR
-- undescribed --
.SH "DESCRIPTION"
.PP
\fImapping\fR - address_space which was dirtied
.PP
Processes which are dirtying memory should call in here once for each page
which was newly dirtied.  The function will periodically check the system's
dirty state and will initiate writeback if needed.
.PP
On really big machines, get_page_state is expensive, so try to avoid calling
it too often (ratelimiting).  But once we're over the dirty memory limit we
decrease the ratelimiting by a lot, to prevent individual processes from
overshooting the limit by (ratelimit_pages) each.