invalidate_mapping_pages(9) [centos man page]

INVALIDATE_MAPPING_P(9) 				    Memory Management in Linux					   INVALIDATE_MAPPING_P(9)

NAME

       invalidate_mapping_pages - Invalidate all the unlocked pages of one inode

SYNOPSIS

       unsigned long invalidate_mapping_pages(struct address_space * mapping, pgoff_t start, pgoff_t end);

ARGUMENTS

       mapping
	   the address_space which holds the pages to invalidate

       start
	   the offset 'from' which to invalidate

       end
	   the offset 'to' which to invalidate (inclusive)

DESCRIPTION

       This function only removes the unlocked pages, if you want to remove all the pages of one inode, you must call truncate_inode_pages.

       invalidate_mapping_pages will not block on IO activity. It will not invalidate pages which are dirty, locked, under writeback or mapped
       into pagetables.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   INVALIDATE_MAPPING_P(9)

WRITE_CACHE_PAGES(9)					    Memory Management in Linux					      WRITE_CACHE_PAGES(9)

NAME

       write_cache_pages - walk the list of dirty pages of the given address space and write all of them.

SYNOPSIS

       int write_cache_pages(struct address_space * mapping, struct writeback_control * wbc, writepage_t writepage, void * data);

ARGUMENTS

       mapping
	   address space structure to write

       wbc
	   subtract the number of written pages from *wbc->nr_to_write

       writepage
	   function called for each page

       data
	   data passed to writepage function

DESCRIPTION

       If a page is already under I/O, write_cache_pages skips it, even if it's dirty. This is desirable behaviour for memory-cleaning writeback,
       but it is INCORRECT for data-integrity system calls such as fsync.  fsync and msync need to guarantee that all the data which was dirty at
       the time the call was made get new I/O started against them. If wbc->sync_mode is WB_SYNC_ALL then we were called for data integrity and we
       must wait for existing IO to complete.

       To avoid livelocks (when other process dirties new pages), we first tag pages which should be written back with TOWRITE tag and only then
       start writing them. For data-integrity sync we have to be careful so that we do not miss some pages (e.g., because some other process has
       cleared TOWRITE tag we set). The rule we follow is that TOWRITE tag can be cleared only by the process clearing the DIRTY tag (and
       submitting the page for IO).

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						      WRITE_CACHE_PAGES(9)