johan...@sun.com wrote:
On Thu, Jul 09, 2009 at 12:18:17PM -0500, Bob Friesenhahn wrote:
Do madvise() options like MADV_ACCESS_LWP and MADV_ACCESS_MANY work on
memory allocated via malloc()? If MADV_ACCESS_LWP is specified and
malloc() hands out heap memory which has been used before (e.g. by some
other LWP), is the memory data in the range moved (physically copied and
remapped to the same address via VM subsystem) closest to the CPU core
which next touches it?
Currently, segvn is the only segment driver with support for madvise
opertaions;
This part isn't exactly right. madvise(3C) is also supported by the
segspt virtual memory segment driver for Intimate Shared Memory (ISM)
along with segvn.
Jonathan
_______________________________________________
perf-discuss mailing list
perf-discuss@opensolaris.org
