From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
Peter Zijlstra <peterz@infradead.org>,
gorcunov@openvz.org, luto@amacapital.net, keescook@chromium.org,
willy@infradead.org, torvalds@linux-foundation.org,
tglx@linutronix.de, bp@suse.de, andy.shevchenko@gmail.com,
linux-kernel@vger.kernel.org, hpa@zytor.com,
ebiederm@xmission.com, jgross@suse.com,
linux-tip-commits@vger.kernel.org,
Dave Hansen <dave.hansen@intel.com>
Subject: Re: [tip:x86/mm] x86/boot/compressed/64: Describe the logic behind the LA57 check
Date: Mon, 12 Mar 2018 17:50:49 +0300 [thread overview]
Message-ID: <20180312145049.boh3wmaotim6sfh2@black.fi.intel.com> (raw)
In-Reply-To: <20180312143212.77z2ptyqbsbqdll3@gmail.com>
On Mon, Mar 12, 2018 at 02:32:12PM +0000, Ingo Molnar wrote:
>
> * Kirill A. Shutemov <kirill@shutemov.name> wrote:
>
> > > We can of course bike shed / benchmark this once my desktop refresh
> > > sports this feature, but ISTR this being one of the very first things
> > > Ingo mentioned when we started this whole 5L thing.
> >
> > I would rather not fix the problem that may not actually exist. :)
>
> That 5 level pagetables involve more overhead is a realy problem.
As I mentioned before, microarchitecture changes takes care about
additional overhead: size of intermediate TLB was increased which should
make the difference between 4- and 5-level paging negligible.
> By default we should only enable 5-level paging if memory mappings exist in
> the memory map that require the extended physical memory space.
I disagree that we should decide usefulness of the 5-level paging based on
size of physical memory on the machine.
Consider use case when you have 100TiB database file. It's pretty
reasonable to mmap() such file at once even if you don't have 100TiB of
physical memory to back it up. 1/100 of the file size may still work
fairly well.
Virtual address space is useful on its own and we shouldn't take the
value from the user just because he doesn't have tens of terabytes of
memory.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2018-03-12 14:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 18:04 [PATCH 0/5] x86/boot/compressed/64: Prepare trampoline memory Kirill A. Shutemov
2018-02-26 18:04 ` [PATCH 1/5] x86/boot/compressed/64: Describe the logic behind LA57 check Kirill A. Shutemov
2018-03-12 9:27 ` [tip:x86/mm] x86/boot/compressed/64: Describe the logic behind the " tip-bot for Kirill A. Shutemov
2018-03-12 12:40 ` Peter Zijlstra
2018-03-12 12:43 ` Kirill A. Shutemov
2018-03-12 13:10 ` Peter Zijlstra
2018-03-12 14:04 ` Kirill A. Shutemov
2018-03-12 14:32 ` Ingo Molnar
2018-03-12 14:50 ` Kirill A. Shutemov [this message]
2018-03-12 16:42 ` Linus Torvalds
2018-03-12 17:06 ` Andy Lutomirski
2018-03-12 17:12 ` Linus Torvalds
2018-03-12 17:41 ` Ingo Molnar
2018-03-12 17:21 ` Dave Hansen
2018-03-12 14:52 ` Cyrill Gorcunov
2018-02-26 18:04 ` [PATCH 2/5] x86/boot/compressed/64: Find a place for 32-bit trampoline Kirill A. Shutemov
2018-02-26 22:30 ` Borislav Petkov
2018-02-27 8:14 ` Kirill A. Shutemov
2018-03-12 9:28 ` [tip:x86/mm] " tip-bot for Kirill A. Shutemov
2018-02-26 18:04 ` [PATCH 3/5] x86/boot/compressed/64: Save and restore trampoline memory Kirill A. Shutemov
2018-03-12 9:29 ` [tip:x86/mm] " tip-bot for Kirill A. Shutemov
2018-02-26 18:04 ` [PATCH 4/5] x86/boot/compressed/64: Set up " Kirill A. Shutemov
2018-03-12 9:29 ` [tip:x86/mm] " tip-bot for Kirill A. Shutemov
2018-02-26 18:04 ` [PATCH 5/5] x86/boot/compressed/64: Prepare new top-level page table for trampoline Kirill A. Shutemov
2018-03-12 9:30 ` [tip:x86/mm] " tip-bot for Kirill A. Shutemov
2018-02-26 19:32 ` [PATCH 0/5] x86/boot/compressed/64: Prepare trampoline memory Borislav Petkov
2018-02-26 20:55 ` Kirill A. Shutemov
2018-02-27 9:32 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180312145049.boh3wmaotim6sfh2@black.fi.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=bp@suse.de \
--cc=dave.hansen@intel.com \
--cc=ebiederm@xmission.com \
--cc=gorcunov@openvz.org \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=keescook@chromium.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®