[lkml]   [2017]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v3] powerpc: mm: support ARCH_MMAP_RND_BITS
On Thu, Apr 13, 2017 at 12:39 PM, Balbir Singh <> wrote:
>>> Yes. It was derived from TASK_SIZE :
>> That is getting update to 128TB by default and conditionally to 512TB
> Since this is compile time, we should probably keep the scope to 128TB
> for now and see if we want to change things at run time later, since
> the expansion is based on a hint. Suggestions?

I think this makes sense. If the conditional expansion to 512TB is
protected by a kconfig symbol, we can use the same to have separate
ranges for 128TB and 512TB using the kconfig symbol as the
differentiating factor.

Also please let me know which branch/tree to use where we are done
with the change making the default to 128TB. My v2 was based on
(mater branch), where the TASK_SIZE is set to 46-bits inside

So that I can spin the v3 accordingly.


 \ /
  Last update: 2017-04-17 06:49    [W:0.043 / U:0.752 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site