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

.SH NAME
ntfs_writepage \- write a page to the backing store
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
int ntfs_writepage  (struct page * \fIpage\fB, struct writeback_control * \fIwbc\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIpage\fB\fR
page cache page to write out
.TP
\fB\fIwbc\fB\fR
-- undescribed --
.SH "DESCRIPTION"
.PP
For non-resident attributes, \fBntfs_writepage\fR writes the \fIpage\fR by calling
the ntfs version of the generic \fBblock_write_full_page\fR function,
\fBntfs_write_block\fR, which in turn if necessary creates and writes the
buffers associated with the page asynchronously.
.PP
For resident attributes, OTOH, \fBntfs_writepage\fR writes the \fIpage\fR by copying
the data to the mft record (which at this stage is most likely in memory).
Thus, in this case, I/O is synchronous, as even if the mft record is not
cached at this point in time, we need to wait for it to be read in before we
can do the copy.
.PP
Note the caller clears the page dirty flag before calling \fBntfs_writepage\fR\&.
.PP
Based on \fBntfs_readpage\fR and fs/buffer.c::\fBblock_write_full_page\fR\&.
.PP
Return 0 on success and -errno on error.