All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	paulus@samba.org, mpe@ellerman.id.au
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH 5/5] powerpc/mm/hash: Increase VA range to 256TB
Date: Tue, 07 Feb 2017 15:06:13 +1100	[thread overview]
Message-ID: <1486440373.4850.114.camel@kernel.crashing.org> (raw)
In-Reply-To: <1486439333-22162-6-git-send-email-aneesh.kumar@linux.vnet.ibm.com>

That's 48 bits. I would keep the limit at 47 without some explicit
opt-in by applications. That's what users get on x86 and we know
some GPUs have limits there.

Cheers,
Ben.

  reply	other threads:[~2017-02-07  4:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07  3:48 [RFC PATCH 0/5] Add support for larger address space for ppc64 Aneesh Kumar K.V
2017-02-07  3:48 ` [RFC PATCH 1/5] powerpc/mm/slice: Convert slice_mask high slice to a bitmap Aneesh Kumar K.V
2017-02-08 10:30   ` Balbir Singh
2017-02-07  3:48 ` [RFC PATCH 2/5] powerpc/mm/slice: Update the function prototype Aneesh Kumar K.V
2017-02-07  3:48 ` [RFC PATCH 3/5] powerpc/mm/hash: Move kernel context to the starting of context range Aneesh Kumar K.V
2017-02-07  3:48 ` [RFC PATCH 4/5] powerpc/mm/hash: Support 68 bit VA Aneesh Kumar K.V
2017-02-07  3:48 ` [RFC PATCH 5/5] powerpc/mm/hash: Increase VA range to 256TB Aneesh Kumar K.V
2017-02-07  4:06   ` Benjamin Herrenschmidt [this message]
2017-02-07  4:17     ` Aneesh Kumar K.V
2017-02-07  4:46       ` Benjamin Herrenschmidt

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=1486440373.4850.114.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.