On 1/11/2019 6:28 PM, Mike Kravetz wrote: > On 1/11/19 1:55 PM, Kirill A. Shutemov wrote: >> On Fri, Jan 11, 2019 at 08:10:03PM +0000, Mike Kravetz wrote: >>> At LPC last year, Boaz Harrosh asked why he had to 'jump through hoops' >>> to get an address returned by mmap() suitably aligned for THP. It seems >>> that if mmap is asking for a mapping length greater than huge page >>> size, it should align the returned address to huge page size. A better heuristic would be to return an aligned address if the length is a multiple of the huge page size. The gap (if any) between the end of the previous VMA and the start of this VMA would be filled by subsequent smaller mmap requests. The new behavior would need to become part of the mmap interface definition so apps can rely on it and omit their hoop-jumping code. Personally I would like to see a new MAP_ALIGN flag and treat the addr argument as the alignment (like Solaris), but I am told that adding flags is problematic because old kernels accept undefined flag bits from userland without complaint, so their behavior would change. - Steve >>> THP alignment has already been added for DAX, shm and tmpfs. However, >>> simple anon mappings does not take THP alignment into account. >> >> In general case, when no hint address provided, all anonymous memory >> requests have tendency to clamp into a single bigger VMA and get you >> better chance having THP, even if a single allocation is too small. >> This patch will *reduce* the effect and I guess the net result will be >> net negative. > > Ah! I forgot about combining like mappings into a single vma. Increasing > alignment could/would prevent this. > >> The patch also effectively reduces bit available for ASLR and increases >> address space fragmentation (increases number of VMA and therefore page >> fault cost). >> >> I think any change in this direction has to be way more data driven. > > Ok, I just wanted to ask the question. I've seen application code doing > the 'mmap sufficiently large area' then unmap to get desired alignment > trick. Was wondering if there was something we could do to help. > > Thanks >
