In article <9kkr7r$mov$1@cesium.transmeta.com>,
H. Peter Anvin <hpa@zytor.com> 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).
No, they aren't broken, but they should know that the use of lots of
small memory segments (even if it is a design goal) can and will slow
down page faulting, and use more memory for MM management for example.
Linux does have a log(n) vma lookup, so the slowdown isn't huge.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Aug 07 2001 - 21:00:36 EST