.\" 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" "9" "09 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
writeback control structure
.SH "DESCRIPTION"
.PP
This is called from the VM when it wants to have a dirty ntfs page cache
page cleaned.  The VM has already locked the page and marked it clean.
.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).
The mft record is then marked dirty and written out asynchronously via the
vfs inode dirty code path for the inode the mft record belongs to or via the
vm page dirty code path for the page the mft record is in.
.PP
Based on \fBntfs_readpage\fR and fs/buffer.c::\fBblock_write_full_page\fR\&.
.PP
Return 0 on success and -errno on error.