> - aspacem_maxAddr = (Addr) 0x7fffffffffff; > + aspacem_maxAddr = (Addr) 0x4000000000 - 1; // 256G
Are you sure this frag is right? It seems to have drastically reduced aspacem_maxAddr. It may be that this is a constant that shouldn't change. You can see what the initial memory layout looks like by doing this valgrind -d -d /bin/date and looking at the "<<< SHOW_SEGMENTS: Initial layout (5 segments)" for both the original and patched versions. For the original version, I have --12650:2: aspacem 0: RSVN 0000000000-0003ffffff 64m ----- SmFixed --12650:2: aspacem 1: 0004000000-0801ffffff 32736m --12650:2: aspacem 2: RSVN 0802000000-0802000fff 4096 ----- SmFixed --12650:2: aspacem 3: 0802001000-0fffffffff 32735m --12650:2: aspacem 4: RSVN 1000000000-ffffffffffffffff 16383e ----- SmFixed that is .. 2 32G RSVNs with a 4k guard page in between. If you do it right, I *think* what you should get is 2 128G RSVNs with a 4k guard page in between. J ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
