[lkml]   [2022]   [Jul]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] f2fs: Delete f2fs_copy_page() and replace with memcpy_page()
On 2022/7/17 16:36, Fabio M. De Francesco wrote:
> f2fs_copy_page() is a wrapper around two kmap() + one memcpy() from/to
> the mapped pages. It unnecessarily duplicates a kernel API and it makes
> use of kmap(), which is being deprecated in favor of kmap_local_page().
> Two main problems with kmap(): (1) It comes with an overhead as mapping
> space is restricted and protected by a global lock for synchronization and
> (2) it also requires global TLB invalidation when the kmap’s pool wraps
> and it might block when the mapping space is fully utilized until a slot
> becomes available.
> With kmap_local_page() the mappings are per thread, CPU local, can take
> page faults, and can be called from any context (including interrupts).
> It is faster than kmap() in kernels with HIGHMEM enabled. Therefore, its
> use in __clone_blkaddrs() is safe and should be preferred.
> Delete f2fs_copy_page() and use a plain memcpy_page() in the only one
> site calling the removed function. memcpy_page() avoids open coding two
> kmap_local_page() + one memcpy() between the two kernel virtual addresses.
> Suggested-by: Christoph Hellwig <>
> Suggested-by: Ira Weiny <>
> Signed-off-by: Fabio M. De Francesco <>

Reviewed-by: Chao Yu <>


 \ /
  Last update: 2022-07-24 12:26    [W:0.064 / U:0.564 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site