[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <545AADCC.5030102@intel.com>
Date: Wed, 05 Nov 2014 15:07:56 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Andi Kleen <andi@...stfloor.org>
CC: Masanari Iida <standby24x7@...il.com>,
Jonathan Corbet <corbet@....net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-mm@...ck.org, lcapitulino@...hat.com
Subject: Re: [PATCH] Documentation: vm: Add 1GB large page support information
On 11/05/2014 02:58 PM, Andi Kleen wrote:
>>> >> I understand that there are some exception cases which doesn't support 1G
>>> >> large pages on newer CPUs.
>>> >> I like Dave's example, at the same time I would like to add "pdpe1gb flag" in
>>> >> the document.
>>> >>
>>> >> For example, x86 CPUs normally support 4K and 2M (1G if pdpe1gb flag exist).
>> >
>> > Is 1G supported on CPUs that have pdpe1gb and are running a 32-bit kernel?
> No, 1GB pages is a 64bit only feature.
This is one sentence in a document that nobody reads, so we're all
putting way more brainpower in to this than we should.
We can't universally say that "1G if pdpe1gb flag exist" since a 64-bit
CPU running a 32-bit kernel doesn't support 1G pages *despite* the
presence of pdpe1gb. I think that makes it a pretty crappy thing to put
in a document since it's just misleading. We can't spell out all the
pitfalls or all the possible combinations, and it's not the place of our
stupid documentation to repeat what's in the architecture manuals.
For example, x86 CPUs normally support 4K and 2M (1G if
architecturally supported).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists