Commit ea1754a0 authored by Kirill A. Shutemov's avatar Kirill A. Shutemov Committed by Linus Torvalds
Browse files

mm, fs: remove remaining PAGE_CACHE_* and page_cache_{get,release} usage 



Mostly direct substitution with occasional adjustment or removing
outdated comments.

Signed-off-by: default avatarKirill A. Shutemov <kirill.shutemov@linux.intel.com>
Acked-by: default avatarMichal Hocko <mhocko@suse.com>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent 09cbfeaf

Documentation/filesystems/cramfs.txt

+1 −1
Original line number Diff line number Diff line
@@ -38,7 +38,7 @@ the update lasts only as long as the inode is cached in memory, after 
which the timestamp reverts to 1970, i.e. moves backwards in time.



Currently, cramfs must be written and read with architectures of the

same endianness, and can be read only by kernels with PAGE_CACHE_SIZE

same endianness, and can be read only by kernels with PAGE_SIZE

== 4096.  At least the latter of these is a bug, but it hasn't been

decided what the best fix is.  For the moment if you have larger pages

you can just change the #define in mkcramfs.c, so long as you don't

Documentation/filesystems/tmpfs.txt

+1 −1
Original line number Diff line number Diff line
@@ -60,7 +60,7 @@ size: The limit of allocated bytes for this tmpfs instance. The 
           default is half of your physical RAM without swap. If you

           oversize your tmpfs instances the machine will deadlock

           since the OOM handler will not be able to free that memory.

nr_blocks: The same as size, but in blocks of PAGE_CACHE_SIZE.

nr_blocks: The same as size, but in blocks of PAGE_SIZE.

nr_inodes: The maximum number of inodes for this instance. The default

           is half of the number of your physical RAM pages, or (on a

           machine with highmem) the number of lowmem RAM pages,

Documentation/filesystems/vfs.txt

+2 −2
Original line number Diff line number Diff line
@@ -708,9 +708,9 @@ struct address_space_operations { 
	from the address space.  This generally corresponds to either a

	truncation, punch hole  or a complete invalidation of the address

	space (in the latter case 'offset' will always be 0 and 'length'

	will be PAGE_CACHE_SIZE). Any private data associated with the page

	will be PAGE_SIZE). Any private data associated with the page

	should be updated to reflect this truncation.  If offset is 0 and

	length is PAGE_CACHE_SIZE, then the private data should be released,

	length is PAGE_SIZE, then the private data should be released,

	because the page must be able to be completely discarded.  This may

	be done by calling the ->releasepage function, but in this case the

	release MUST succeed.

arch/parisc/mm/init.c

+1 −1
Original line number Diff line number Diff line
@@ -22,7 +22,7 @@ 
#include <linux/swap.h>

#include <linux/unistd.h>

#include <linux/nodemask.h>	/* for node_online_map */

#include <linux/pagemap.h>	/* for release_pages and page_cache_release */

#include <linux/pagemap.h>	/* for release_pages */

#include <linux/compat.h>



#include <asm/pgalloc.h>

block/bio.c

+2 −2
Original line number Diff line number Diff line
@@ -1615,8 +1615,8 @@ static void bio_release_pages(struct bio *bio) 
 * the BIO and the offending pages and re-dirty the pages in process context.

 *

 * It is expected that bio_check_pages_dirty() will wholly own the BIO from

 * here on.  It will run one page_cache_release() against each page and will

 * run one bio_put() against the BIO.

 * here on.  It will run one put_page() against each page and will run one

 * bio_put() against the BIO.

 */



static void bio_dirty_fn(struct work_struct *work);