Skip to contentSkip to conversation

/proc/<n>/maps growing...

DISCUSSION Rick Hohensee 1 participant 1 message Aug 7, 2001

lore
Share & tools
lore
#0 lore raw
Quoted 5 lines
Quoted 3 lines

I believe the best way is to allocate always the new vma, and to hide the merging into the lowlevel of a new insert_vm_struct (with a special function ala merge_segments that we can share with mprotect like in

2.2).

Torvalds

Quoted 4 lines

Oh, and THAT is going to speed things up?

Hint: the merging actually happens at a fairly high percentage for the common cases. We win more by walking the tree twice and avoiding the

BROWNNOSE
No, I have nothing to say about malloc/mmap/etc. I just want to add some balancing positiveness to offset my usual polemics. Torvalds harps on optimizing for the common case all the time. This little voice with a faint scandanavian accent in the back of my head keeps saying "optimize for the common case". It is a wise little voice. The common case is usually beyond the ken of a compiler, it's something a human has to know, it works, can pay off huge, and works with anything from assembly to Bash.
END BROWNNOSE
RESUME FLAMEBAIT

Rick Hohensee
www.clienux.com