The one question I have is whether ISM (Intimate Shared Memory) segments are immune to being coerced to relocate via pmadvise(3c)? I've tried it without success. A quick look at the seg_spt.c code seemed to indicate that when an spt segment is created its lgroup policy is set to LGRP_MEM_POLICY_DEFAULT that will result in randomized allocation for segments greater than 8MB. I've verified as much using the NUMA enhanced pmap(3c) command.
I have an ISM segment that gets consumed by HW that is limited to 32-bit addressing and thus have a need to control the physical range that backs the segment. At this point, it would seem that I need to allocate the memory (about 300MB) in the kernel and map it back to user-land but I would lose the use of 2MB pages since I have not quite figured out how to allocate memory using a particular page size. Have I misinterpreted the code? Do I have other options?
Thanks,
--Marc
_______________________________________________ perf-discuss mailing list perf-discuss@opensolaris.org
