Lines Matching refs:writepage

190 	int (*writepage)(struct page *page, struct writeback_control *wbc);
220 writepage:		yes, unlocks (see below)
250 	->writepage() is used for two purposes: for "memory cleansing" and for
254 If writepage is called for sync (wbc->sync_mode != WBC_SYNC_NONE) then
258 If writepage is called for memory cleansing (sync_mode ==
260 possible.  So writepage should try to avoid blocking against
273 caller, unless ->writepage() returns special WRITEPAGE_ACTIVATE
275 currently, and VM should stop calling ->writepage() on this page for some
280 and return zero, writepage *must* run set_page_writeback() against the page,
285 writepage.
293 set_page_writeback()/end_page_writeback() on a page submitted to writepage