greetings, all ---
this is a follow_up to my recent inquiry.
a while back, i took apart mr. kamp's malloc(3), so, i have a fair idea of its
operation.
i have not, as yet, done the same for its replacement.
therefore, treat these questions, regarding je_malloc(3), as coming from a user.
q: given that brk(2) and sbrk(2) can fail due to an interaction with the
swapper,
does mmap(2) suffer from the same issue,
given that it has to "look up" the things that brk(2) already knows
about ?
q: if mmap(2) does not have this problem,
then does that mean that if i use only the "m" option to je_malloc(3),
it will fail only when it --really_is-- out_of_memory,
including insufficient data_size resource_limit
[ increasing resource_limits are a separate topic ] ?
q: if mmap(2) --does-- still have this interaction,
then should i continue to check resource_limits to be sure ?
separately,
q: is gcc(1) still at 4.2.1 ?
q: if so, what plans are there for which next_version and when ?
tia.
rob
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
