Re: [PATCH v21 1/4] mm: add VM_DROPPABLE for designating always lazily freeable mappings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08.07.24 15:57, Jason A. Donenfeld wrote:
On Mon, Jul 08, 2024 at 10:23:10AM +0200, David Hildenbrand wrote:
As a side note, I'll raise that I am not a particular fan of the
"droppable" terminology, at least with the "read 0s" approach.

   From a user perspective, the memory might suddenly lose its state and
read as 0s just like volatile memory when it loses power. "dropping
pages" sounds more like an implementation detail.

Long story short: it's the hypervisor that could be effectively
dropping/zeroing out that memory, not the guest VM. "NONVOLATILE" might
be clearer than "DROPPABLE".

Surely you mean "VOLATILE", not "NONVOLATILE", right?

Yes, typo :)

--
Cheers,

David / dhildenb





[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux