Skip to content

RFC Some remote_vm folio conversions

Vishal Moola (Oracle) linux-mm lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest3 patches 5 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3mm/memory.c: convert __copy_remote_vm_str() to foliosmm/memory.c+16 -95 replies
2/3mm/memory.c: convert __access_remote_vm() to foliosmm/memory.c+16 -110 replies
3/3mm: Remove unmap_and_put_page()include/linux/highmem.h+0 -60 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC PATCH 0/3] Some remote_vm folio conversions

Both callers of unmap_and_put_page() are for tracing purposes and interact with user vmas. In a memdesc world, these should end up operating on folios, so convert them.

This patchset converts those functions so that gup - namely get_user_page_vma_remote() - can eventually safely pass around large folios.

This iteration does NOT allow support for handling a large folio all at once, it merely makes working on subpages of a large folio safe. Does anyone have any thoughts on if we might want to handle these in larger than PAGE_SIZE chunks? It seems like a lot of work with how kmap() works right now...

On a similar note, might we want to convert implementations of copy_{to,from}_user_page() to pass around folios as well?

Vishal Moola (Oracle) (3):
mm/memory.c: convert __copy_remote_vm_str() to folios mm/memory.c: convert __access_remote_vm() to folios
mm: Remove unmap_and_put_page()

 include/linux/highmem.h |  6 -----
 mm/memory.c             | 52 +++++++++++++++++++++++++----------------
 2 files changed, 32 insertions(+), 26 deletions(-)
Signature · 1 line
2.49.0