Home
last modified time | relevance | path

Searched refs:AOP_WRITEPAGE_ACTIVATE (Results 1 – 12 of 12) sorted by relevance

/linux-4.1.27/fs/gfs2/
Daops.c296 if (ret == AOP_WRITEPAGE_ACTIVATE) { in gfs2_write_jdata_pagevec()
/linux-4.1.27/fs/f2fs/
Dcheckpoint.c211 return AOP_WRITEPAGE_ACTIVATE; in f2fs_write_meta_page()
Ddata.c1499 return AOP_WRITEPAGE_ACTIVATE; in f2fs_write_data_page()
Dnode.c1345 return AOP_WRITEPAGE_ACTIVATE; in f2fs_write_node_page()
/linux-4.1.27/mm/
Dmigrate.c675 if (rc != AOP_WRITEPAGE_ACTIVATE) in writeout()
Dpage-writeback.c1938 if (ret == AOP_WRITEPAGE_ACTIVATE) { in write_cache_pages()
Dvmscan.c558 if (res == AOP_WRITEPAGE_ACTIVATE) { in pageout()
Dshmem.c842 return AOP_WRITEPAGE_ACTIVATE; /* Return with page locked */ in shmem_writepage()
/linux-4.1.27/include/linux/
Dfs.h301 AOP_WRITEPAGE_ACTIVATE = 0x80000, enumerator
/linux-4.1.27/Documentation/filesystems/
Dvfs.txt618 should return AOP_WRITEPAGE_ACTIVATE so that the VM will not keep
/linux-4.1.27/fs/btrfs/
Dextent_io.c4058 if (unlikely(ret == AOP_WRITEPAGE_ACTIVATE)) { in extent_write_cache_pages()
Dinode.c8437 return AOP_WRITEPAGE_ACTIVATE; in btrfs_writepage()