Skip to contentSkip to conversation

mincore on anon mappings

DISCUSSION Andi Kleen 2 participants 2 messages Jun 19, 2004 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andi Kleen

author
#2 lore raw
Quoted 8 lines · David S. Miller

Therefore I propose we add a MAP_FORCE which does exactly what GCC wants which is:

1) The passed in 'hint' address is treated as mandatory, if exactly that address cannot be used, we fail.

2) Existing areas get in the way, and cause failure.

That sounds unintuitive. I would expect MAP_FORCE to do exactly that (that is is done by default right now is a different story). But you want to reverse the meaning.

How about calling it MAP_STRICT or just MAP_CHECK ?

Quoted 3 lines

3) get_unmapped_area() implementations shut off any 'hint' address modification logic they may have.

Good idea definitely.

-Andi

#3 lore raw
Quoted 1 line · On Sun, 20 Jun 2004 02:05:19 +0200 Andi Kleen <[email protected]> wrote:

How about calling it MAP_STRICT or just MAP_CHECK ?

MAP_STRICT sounds fine to me.