Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 17 Apr 2017 10:18:09 +0530
From: Bhupesh SHARMA <>
To: Balbir Singh <>
Cc: "Aneesh Kumar K.V" <>, Bhupesh Sharma <>, 
	Kees Cook <>,, 
	Alistair Popple <>, 
	"" <>, Scott Wood <>, 
	Paul Mackerras <>, Alexander Graf <>, Daniel Cashman <>, 
	Anatolij Gustschin <>, 
	"open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)" <>, Daniel Cashman <>
Subject: Re: [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.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.