From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [RFC PATCH 1/4] libnvdimm/namespace: Make namespace size validation arch dependent
Date: Thu, 31 Oct 2019 14:07:49 +0530 [thread overview]
Message-ID: <8e29b94c-cb82-2632-965c-567d26791f76@linux.ibm.com> (raw)
In-Reply-To: <CAPcyv4h42_1deZDaaW1RqX0Ls+maiFO_1e=6xJuHTa3wdWvVvA@mail.gmail.com>
On 10/31/19 12:00 PM, Dan Williams wrote:
> On Wed, Oct 30, 2019 at 10:35 PM Aneesh Kumar K.V
> <aneesh.kumar@linux.ibm.com> wrote:
> [..]
>
>
> All that said, the x86 vmemmap_populate() falls back to use small
> pages in some case to get around this constraint. Can't powerpc do the
> same? It would seem to be less work than the above proposal.
>
ppc64 supports two translation mode (radix and hash). We can do the
above with radix translation. With hash we use just one page size( in
this specific case 16MB) for direct-map mapping.
-aneesh
next prev parent reply other threads:[~2019-10-31 8:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 9:48 [RFC PATCH 1/4] libnvdimm/namespace: Make namespace size validation arch dependent Aneesh Kumar K.V
2019-10-28 9:48 ` [RFC PATCH 2/4] libnvdimm/namespace: Disable the region if the namespace size is not aligned correctly Aneesh Kumar K.V
2019-10-28 9:48 ` [RFC PATCH 3/4] libnvdimm/namespace: Use direct-mapping page size to validate namespace size Aneesh Kumar K.V
2019-10-28 9:48 ` [RFC PATCH 4/4] libnvdimm/namespace: Add debug check while initializing namespace resource size Aneesh Kumar K.V
2019-10-28 21:21 ` [RFC PATCH 1/4] libnvdimm/namespace: Make namespace size validation arch dependent Ira Weiny
2019-10-29 4:34 ` Aneesh Kumar K.V
2019-10-28 23:08 ` Dan Williams
2019-10-29 4:34 ` Aneesh Kumar K.V
2019-10-29 5:30 ` Dan Williams
2019-10-31 5:35 ` Aneesh Kumar K.V
2019-10-31 6:30 ` Dan Williams
2019-10-31 8:37 ` Aneesh Kumar K.V [this message]
2019-10-31 15:53 ` Dan Williams
2019-11-06 10:44 ` Aneesh Kumar K.V
2019-11-16 12:15 ` Aneesh Kumar K.V
2019-11-16 18:50 ` Dan Williams
2019-11-18 9:51 ` Aneesh Kumar K.V
2019-11-19 17:58 ` Dan Williams
2019-11-20 3:19 ` Aneesh Kumar K.V
2019-11-20 3:46 ` Dan Williams
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=8e29b94c-cb82-2632-965c-567d26791f76@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=linux-nvdimm@lists.01.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).