diff options
author | Vishal Verma <vishal.l.verma@intel.com> | 2016-04-21 16:45:56 -0400 |
---|---|---|
committer | Vishal Verma <vishal.l.verma@intel.com> | 2016-05-18 14:16:58 -0400 |
commit | 40543f62cbdce42633e3fe10923099feee272e1f (patch) | |
tree | a42d0be3bb305e19628b3d118ad4be9a80fbc4a8 | |
parent | 4b0228fa1d753f77fe0e6cf4c41398ec77dfbd2a (diff) |
dax: fix a comment in dax_zero_page_range and dax_truncate_page
The distinction between PAGE_SIZE and PAGE_CACHE_SIZE was removed in
09cbfea mm, fs: get rid of PAGE_CACHE_* and page_cache_{get,release}
macros
The comments for the above functions described a distinction between
those, that is now redundant, so remove those paragraphs
Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
-rw-r--r-- | fs/dax.c | 12 |
1 files changed, 0 insertions, 12 deletions
@@ -995,12 +995,6 @@ EXPORT_SYMBOL_GPL(__dax_zero_page_range); | |||
995 | * page in a DAX file. This is intended for hole-punch operations. If | 995 | * page in a DAX file. This is intended for hole-punch operations. If |
996 | * you are truncating a file, the helper function dax_truncate_page() may be | 996 | * you are truncating a file, the helper function dax_truncate_page() may be |
997 | * more convenient. | 997 | * more convenient. |
998 | * | ||
999 | * We work in terms of PAGE_SIZE here for commonality with | ||
1000 | * block_truncate_page(), but we could go down to PAGE_SIZE if the filesystem | ||
1001 | * took care of disposing of the unnecessary blocks. Even if the filesystem | ||
1002 | * block size is smaller than PAGE_SIZE, we have to zero the rest of the page | ||
1003 | * since the file might be mmapped. | ||
1004 | */ | 998 | */ |
1005 | int dax_zero_page_range(struct inode *inode, loff_t from, unsigned length, | 999 | int dax_zero_page_range(struct inode *inode, loff_t from, unsigned length, |
1006 | get_block_t get_block) | 1000 | get_block_t get_block) |
@@ -1035,12 +1029,6 @@ EXPORT_SYMBOL_GPL(dax_zero_page_range); | |||
1035 | * | 1029 | * |
1036 | * Similar to block_truncate_page(), this function can be called by a | 1030 | * Similar to block_truncate_page(), this function can be called by a |
1037 | * filesystem when it is truncating a DAX file to handle the partial page. | 1031 | * filesystem when it is truncating a DAX file to handle the partial page. |
1038 | * | ||
1039 | * We work in terms of PAGE_SIZE here for commonality with | ||
1040 | * block_truncate_page(), but we could go down to PAGE_SIZE if the filesystem | ||
1041 | * took care of disposing of the unnecessary blocks. Even if the filesystem | ||
1042 | * block size is smaller than PAGE_SIZE, we have to zero the rest of the page | ||
1043 | * since the file might be mmapped. | ||
1044 | */ | 1032 | */ |
1045 | int dax_truncate_page(struct inode *inode, loff_t from, get_block_t get_block) | 1033 | int dax_truncate_page(struct inode *inode, loff_t from, get_block_t get_block) |
1046 | { | 1034 | { |