cause I'm writing high performance user-level scheduler and need to reduce as much overhead as possible including page_faults. Thanks for the hint.
Question 2 - Malloc does not guarantee that it will assign the same virtual addr every time you run the same program I think its to do with protecting against buffer overflow attack. In my scenario I have the same program running on different machines and wish to align the malloced regions on both machines. With the current implementation of malloc its not possible. Is there work around maybe a lower level allocation function that does not arbitrary offset the virtual addrs?
If I were you, I'd let malloc allocate whatever memory it wants, and use deltas instead of pointers. This way you make you data structure location independant.
mlock/mlockall
yes. why do you ask?
performance
cause I'm writing high performance user-level scheduler and need to reduce as much overhead as possible including page_faults. Thanks for the hint.
Question 2 - Malloc does not guarantee that it will assign the same virtual addr every time you run the same program I think its to do with protecting against buffer overflow attack. In my scenario I have the same program running on different machines and wish to align the malloced regions on both machines. With the current implementation of malloc its not possible. Is there work around maybe a lower level allocation function that does not arbitrary offset the virtual addrs?
brk/sbrk
ok I think I'vw managed by using sbrk
If I were you, I'd let
If I were you, I'd let malloc allocate whatever memory it wants, and use deltas instead of pointers. This way you make you data structure location independant.
just my $0.02
use mmap instead of
use mmap instead of malloc
and use map_locked and map_fixed
man mmap for ore info....