lkml.org 
[lkml]   [2016]   [Dec]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC, PATCHv1 00/28] 5-level paging
    On Fri, Dec 09, 2016 at 08:40:11AM -0800, Andi Kleen wrote:
    > > On other hand, large virtual address space would put more pressure on
    > > cache -- at least one more page table per process, if we make 56-bit VA
    > > default.
    >
    > The top level page always has to be there unless you disable it at boot time
    > (unless you go for a scheme where some processes share top level pages, and
    > others do not, which would likely be very complicated)
    >
    > But even with that it is more than one: A typical set up has at least two extra
    > 4K pages overhead, one for the bottom and one for the top mappings. Could easily be
    > more.

    So, right, one page for pgd, which we can't easily avoid.

    If we limit VA to 47-bits by default, we would have one p4d page as the
    range will be covered by one entry in pgd.

    If we go to 56-bits VA by default, we would have at least two p4d pages
    even for small processes. This where mine "at least one more page table
    per process" comes from.

    That's waste of memory and potentially cache. I don't think it's
    justified.

    --
    Kirill A. Shutemov

    \
     
     \ /
      Last update: 2016-12-09 18:21    [W:3.218 / U:0.348 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site