Re: [PATCH v1 03/14] mm: add iomem vma selection for memory migration

From
Christoph Hellwig <hch@lst.de>
Date
2021-09-01 08:29:30
Also in
amd-gfx, linux-mm, linux-xfs
Reply to
Felix Kuehling, 2021-08-30
On Mon, Aug 30, 2021 at 01:04:43PM -0400, Felix Kuehling wrote:
quoted
quoted
driver code is not really involved in updating the CPU mappings. Maybe
it's something we need to do in the migration helpers.
It looks like I'm totally misunderstanding what you are adding here
then.  Why do we need any special treatment at all for memory that
has normal struct pages and is part of the direct kernel map?
The pages are like normal memory for purposes of mapping them in CPU
page tables and for coherent access from the CPU.
That's the user page tables.  What about the kernel direct map?
If there is a normal kernel struct page backing there really should
be no need for the pgmap.
From an application
perspective, we want file-backed and anonymous mappings to be able to
use DEVICE_PUBLIC pages with coherent CPU access. The goal is to
optimize performance for GPU heavy workloads while minimizing the need
to migrate data back-and-forth between system memory and device memory.
I don't really understand that part.  file backed pages are always
allocated by the file system using the pagecache helpers, that is
using the page allocator.  Anonymouns memory also always comes from
the page allocator.
The pages are special in two ways:

 1. The memory is managed not by the Linux buddy allocator, but by the
    GPU driver's TTM memory manager
Why?
 2. We want to migrate data in response to GPU page faults and
    application hints using the migrate_vma helpers
Why? 
Thread (42 messages) 42 messages, 9 authors, last reply 2021-09-09
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help