Re: /proc/<n>/maps getting _VERY_ long

[H. Peter Anvin]

Followup to:  <9kl6aa$87l$[e-mail]>
By author:    [e-mail] (Linus Torvalds)
In newsgroup: linux.dev.kernel
>
> In article <9kkr7r$mov$[e-mail]>,
> H. Peter Anvin <[e-mail]> wrote:
> >
> >Do you count applications which selectively mprotect()'s memory (to
> >trap SIGSEGV and maintain coherency with on-disk data structures) as
> >"broken applications"?
> >
> >Such applications *can* use large amounts of mprotect()'s.
> 
> Note that such applications tend to not get any advantage from merging -
> it does in fact only slow things down (because then the next mprotect
> just has to split the thing again).
> 

Unless you're doing a sequential access in the data space, for example
while accessing a large object.  If a single large object (usually
called a BLOB) covers N pages, and is accessed in its entirety, you
will typically have N pagefaults, each of which bring/unprotect the
page and then mprotect() it accordingly.  Those could all be merged
back into a single vma.

Now, I don't know how frequently this actually happens, but I do think
it is at least a possibility.

	-hpa
-- 
<[e-mail]> at work, <[e-mail]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<[e-mail]>