On Mon, Nov 02, 2020 at 10:11:12AM +0100, David Hildenbrand wrote: > On 24.09.20 15:28, Mike Rapoport wrote: > > From: Mike Rapoport <rppt@xxxxxxxxxxxxx> > > > > Hi, > > > > This is an implementation of "secret" mappings backed by a file descriptor. > > I've dropped the boot time reservation patch for now as it is not strictly > > required for the basic usage and can be easily added later either with or > > without CMA. > > Hi Mike, > > I'd like to stress again that I'd prefer *any* secretmem allocations going > via CMA as long as these pages are unmovable. The user can allocate a > non-significant amount of unmovable allocations only fenced by the mlock > limit, which behave very different to mlocked pages - they are not movable > for page compaction/migration. > > Assume you have a system with quite some ZONE_MOVABLE memory (esp. in > virtualized environments), eating up a significant amount of !ZONE_MOVABLE > memory dynamically at runtime can lead to non-obvious issues. It looks like > you have plenty of free memory, but the kernel might still OOM when trying > to do kernel allocations e.g., for pagetables. With CMA we at least know > what we're dealing with - it behaves like ZONE_MOVABLE except for the owner > that can place unmovable pages there. We can use it to compute statically > the amount of ZONE_MOVABLE memory we can have in the system without doing > harm to the system. Why would you say that secretmem allocates from !ZONE_MOVABLE? If we put boot time reservations aside, the memory allocation for secretmem follows the same rules as the memory allocations for any file descriptor. That means we allocate memory with GFP_HIGHUSER_MOVABLE. After the allocation the memory indeed becomes unmovable but it's not like we are eating memory from other zones here. Maybe I'm missing something, but it seems to me that using CMA for any secretmem allocation would needlessly complicate things. > Ideally, we would want to support page migration/compaction and allow for > allocation from ZONE_MOVABLE as well. Would involve temporarily mapping, > copying, unmapping. Sounds feasible, but not sure which roadblocks we would > find on the way. We can support migration/compaction with temporary mapping. The first roadblock I've hit there was that migration allocates 4K destination page and if we use it in secret map we are back to scrambling the direct map into 4K pieces. It still sounds feasible but not as trivial :) But again, there is nothing in the current form of secretmem that prevents allocation from ZONE_MOVABLE. > [...] > > > I've hesitated whether to continue to use new flags to memfd_create() or to > > add a new system call and I've decided to use a new system call after I've > > started to look into man pages update. There would have been two completely > > independent descriptions and I think it would have been very confusing. > > This was also raised on lwn.net by "dullfire" [1]. I do wonder if it would > be the right place as well. I lean towards a dedicated syscall because, as I said, to me it would seem less confusing. > [1] https://lwn.net/Articles/835342/#Comments > > > > > Hiding secret memory mappings behind an anonymous file allows (ab)use of > > the page cache for tracking pages allocated for the "secret" mappings as > > well as using address_space_operations for e.g. page migration callbacks. > > > > The anonymous file may be also used implicitly, like hugetlb files, to > > implement mmap(MAP_SECRET) and use the secret memory areas with "native" mm > > ABIs in the future. > > > > As the fragmentation of the direct map was one of the major concerns raised > > during the previous postings, I've added an amortizing cache of PMD-size > > pages to each file descriptor that is used as an allocation pool for the > > secret memory areas. -- Sincerely yours, Mike.
