Lines Matching full:memory

4 Heterogeneous Memory Management (HMM)
7 Provide infrastructure and helpers to integrate non-conventional memory (device
8 memory like GPU on board memory) into regular kernel path, with the cornerstone
9 of this being specialized struct page for such memory (see sections 5 to 7 of
12 HMM also provides optional helpers for SVM (Share Virtual Memory), i.e.,
20 related to using device specific memory allocators. In the second section, I
24 fifth section deals with how device memory is represented inside the kernel.
30 Problems of using a device specific memory allocator
33 Devices with a large amount of on board memory (several gigabytes) like GPUs
34 have historically managed their memory through dedicated driver specific APIs.
35 This creates a disconnect between memory allocated and managed by a device
36 driver and regular application memory (private anonymous, shared memory, or
37 regular file backed memory). From here on I will refer to this aspect as split
39 i.e., one in which any application memory region can be used by a device
42 Split address space happens because devices can only access memory allocated
43 through a device specific API. This implies that all memory objects in a program
48 to copy objects between generically allocated memory (malloc, mmap private, mmap
49 share) and memory allocated through the device driver API (this still ends up
60 might have to duplicate its input data set using the device specific memory
62 various memory copies.
64 Duplicating each library API to accept as input or output memory allocated by
75 I/O bus, device memory characteristics
79 buses only allow basic memory access from device to main memory; even cache
80 coherency is often optional. Access to device memory from a CPU is even more
83 If we only consider the PCIE bus, then a device can access main memory (often
85 a limited set of atomic operations from the device on main memory. This is worse
87 memory and cannot perform atomic operations on it. Thus device memory cannot
88 be considered the same as regular memory from the kernel point of view.
91 and 16 lanes). This is 33 times less than the fastest GPU memory (1 TBytes/s).
92 The final limitation is latency. Access to main memory from the device has an
93 order of magnitude higher latency than when the device accesses its own memory.
102 access any memory but we must also permit any memory to be migrated to device
103 memory while the device is using it (blocking CPU access while it happens).
111 address points to the same physical memory for any valid main memory address in
123 The second mechanism HMM provides is a new kind of ZONE_DEVICE memory that
124 allows allocating a struct page for each page of device memory. Those pages
126 main memory to device memory using existing migration mechanisms and everything
130 memory for the device memory and second to perform migration. Policy decisions
134 back to main memory. For example, when a page backing a given CPU address A is
135 migrated from a main memory page to a device page, then any CPU access to
136 address A triggers a page fault and initiates a migration back to main memory.
140 leverages device memory by migrating the part of the data set that is actively being
255 Represent and manage device memory from core kernel point of view
258 Several different designs were tried to support device memory. The first one
259 used a device specific data structure to keep information about migrated memory
261 addresses that were backed by device memory. It turns out that this ended up
263 paths to be updated to understand this new kind of memory.
265 Most kernel code paths never try to access the memory behind a page
267 directly using struct page for device memory which left most kernel code paths
271 Migration to and from device memory
274 Because the CPU cannot access device memory directly, the device driver must
280 Before migrating pages to device private memory, special device private
283 a page that has been migrated to device private memory.
307 memory (see :ref:`Page migration <page_migration>`) but the steps are split
321    ``MIGRATE_VMA_SELECT_SYSTEM`` will only migrate system memory and
323    device private memory. If the latter flag is set, the ``args->pgmap_owner``
327    system memory and device private memory.
343    This lets the driver allocate device private memory and clear it instead
344    of copying a page of zeros. Valid PTE entries to system memory or
346    from the LRU (if system memory since device private pages are not on
360    system memory page, locks the page with ``lock_page()``, and fills in the
366    invalidate device private MMU mappings and copy device private memory
367    to system memory or another device private page. The core Linux kernel
373    destination or clear the destination device private memory if the pointer
374    is ``NULL`` meaning the source page was not populated in system memory.
408 Exclusive access memory
412 atomic access to system memory. To support atomic operations to a shared virtual
413 memory page such a device needs access to that page which is exclusive of any
415 can be used to make a memory range inaccessible from userspace.
425 Memory cgroup (memcg) and rss accounting
428 For now, device memory is accounted as any regular page in rss counters (either
430 file backed page, or shmem if device page is used for shared memory). This is a
432 memory without knowing about it, running unimpacted.
435 device memory and not a lot of regular system memory and thus not freeing much
436 system memory. We want to gather more real world experience on how applications
437 and system react under memory pressure in the presence of device memory before
438 deciding to account device memory differently.
441 Same decision was made for memory cgroup. Device memory pages are accounted
442 against same memory cgroup a regular page would be accounted to. This does
443 simplify migration to and from device memory. This also means that migration
444 back from device memory to regular memory cannot fail because it would
445 go above memory cgroup limit. We might revisit this choice latter on once we
446 get more experience in how device memory is used and its impact on memory
450 Note that device memory can never be pinned by a device driver nor through GUP
451 and thus such memory is always free upon process exit. Or when last reference
452 is dropped in case of shared memory or file backed memory.