We decide to divide numatop development into 2 phases. At phase 1, numatop is designed as a memory locality characterizing tool. It provides a easy and friendly way for observing performance data from hardware performance counters. Otherwise these data are difficult to interpret.
At phase 2, we hope numatop can provide some clues for the relationship between memory allocation, thread migration and memory access. >From the output of numatop prototype, We often find one case that a thread has high RMA but low LMA, while all NUMA nodes (lgroup leaf nodes) have enough free memory. Why the thread doesn't allocate more memory on it's home affinity node? If it's due to memory allocating after the thread was migrated to another node and then allocate memory on the new node? So in phase 2, we will focus on to find the relationship between the memory access pattern, memory allocation pattern and schedule to get a good memory strategy for application. In brief, numatop phase 1 let the users see something strange in the system, and in phase 2, numatop try to provide some clues. Thanks Jin Yao -- This message posted from opensolaris.org _______________________________________________ perf-discuss mailing list perf-discuss@opensolaris.org
