From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@alien8.de>
Subject: Re: [GIT PULL] x86/mm changes for v4.14: PCID support, 5-level paging support, Secure Memory Encryption support
Date: Mon, 4 Sep 2017 15:23:58 +0300 [thread overview]
Message-ID: <20170904122358.uscplql7tzrnimp4@node.shutemov.name> (raw)
In-Reply-To: <20170904093158.k6pg3ytcbotjlhv5@gmail.com>
On Mon, Sep 04, 2017 at 11:31:58AM +0200, Ingo Molnar wrote:
> The main changes in this cycle are support for three new, complex hardware
> features of x86 CPUs:
>
> - Add 5-level paging support, which is a new hardware feature on upcoming Intel
> CPUs allowing up to 128 PB of virtual address space and 4 PB of physical RAM
> space - a 256-fold increase over the old limits.
Minor nitpick: I don't see where "256-fold" comes from.
Virtual address space increased from 256 TB to 128 PB -- 512 times.
Physical: 64 TB -> 4 PB -- 64 times.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2017-09-04 12:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 9:31 [GIT PULL] x86/mm changes for v4.14: PCID support, 5-level paging support, Secure Memory Encryption support Ingo Molnar
2017-09-04 12:23 ` Kirill A. Shutemov [this message]
2017-09-04 13:01 ` Thomas Gleixner
2017-09-04 13:54 ` Ingo Molnar
2017-09-05 21:17 ` Linus Torvalds
2017-09-05 21:37 ` Andy Lutomirski
2017-09-05 21:44 ` Borislav Petkov
2017-09-05 21:40 ` Ingo Molnar
2017-09-05 21:45 ` Linus Torvalds
2017-09-05 22:33 ` Linus Torvalds
2017-09-05 22:35 ` Andy Lutomirski
2017-09-05 23:09 ` Linus Torvalds
2017-09-06 20:43 ` Jiri Kosina
2017-09-06 21:16 ` Jiri Kosina
2017-09-06 22:26 ` Andy Lutomirski
2017-09-05 21:50 ` Linus Torvalds
2017-09-07 8:07 ` Ingo Molnar
2017-09-07 8:13 ` Ingo Molnar
2017-09-15 11:26 ` Pavel Machek
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=20170904122358.uscplql7tzrnimp4@node.shutemov.name \
--to=kirill@shutemov.name \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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