[lkml]   [2017]   [Nov]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: POWER: Unexpected fault when writing to brk-allocated memory

> If it is decided to keep these kind of heuristics, can we get just a
> small but reasonably precise description of each change to the
> interface and ways for using the new functionality, such that would be
> suitable for the man page? I couldn't fix powerpc because nothing
> matches and even Aneesh and you differ on some details (MAP_FIXED
> behaviour).

I would consider MAP_FIXED as my mistake. We never discussed this
explicitly and I kind of assumed it to behave the same way. ie, we
search in lower address space (128TB) if the hint addr is below 128TB.

IIUC we agree on the below.

1) MAP_FIXED allow the addr to be used, even if hint addr is below 128TB
but hint_addr + len is > 128TB.

2) For everything else we search in < 128TB space if hint addr is below

3) We don't switch to large address space if hint_addr + len > 128TB.
The decision to switch to large address space is primarily based on hint

Is there any other rule we need to outline? Or is any of the above not


 \ /
  Last update: 2017-11-08 21:05    [W:0.101 / U:2.000 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site