.\" 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 "__FILEMAP_FDATAWRITE_RANGE" "9" "09 October 2005" "" ""

.SH NAME
__filemap_fdatawrite_range \- start writeback against all of a mapping's
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
int __filemap_fdatawrite_range  (struct address_space * \fImapping\fB, loff_t \fIstart\fB, loff_t \fIend\fB, int \fIsync_mode\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fImapping\fB\fR
address space structure to write
.TP
\fB\fIstart\fB\fR
offset in bytes where the range starts
.TP
\fB\fIend\fB\fR
offset in bytes where the range ends
.TP
\fB\fIsync_mode\fB\fR
enable synchronous operation
.SH "DESCRIPTION"
.PP
If sync_mode is WB_SYNC_ALL then this is a ``data integrity'' operation, as
opposed to a regular memory * cleansing writeback.  The difference between
these two operations is that if a dirty page/buffer is encountered, it must
be waited upon, and not just skipped over.
.SH "DESCRIPTION"
.PP
If sync_mode is WB_SYNC_ALL then this is a ``data integrity'' operation, as
opposed to a regular memory * cleansing writeback.  The difference between
these two operations is that if a dirty page/buffer is encountered, it must
be waited upon, and not just skipped over.