[RFC PATCH v2 2/2] Architecture defined limit on memory region random shift.

Ilya Smith blackzert at gmail.com
Sat Mar 24 04:48:00 AEDT 2018

> On 22 Mar 2018, at 23:54, Andrew Morton <akpm at linux-foundation.org> wrote:
> Please add changelogs.  An explanation of what a "limit on memory
> region random shift" is would be nice ;) Why does it exist, why are we
> doing this, etc.  Surely there's something to be said - at present this
> is just a lump of random code?
Sorry, my bad. The main idea of this limit is to decrease possible memory
fragmentation. This is not so big problem on 64bit process, but really big for
32 bit processes since may cause failure memory allocation. To control memory
fragmentation and protect 32 bit systems (or architectures) this limit was
introduce by this patch. It could be also moved to CONFIG_ as well.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/linuxppc-dev/attachments/20180323/f5f30ed8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.ozlabs.org/pipermail/linuxppc-dev/attachments/20180323/f5f30ed8/attachment.sig>

More information about the Linuxppc-dev mailing list