On 08/19/2010 06:37 PM, LionSky wrote: >>> >> I have no idea whether "TLB shootdowns" interrupt has any impact on >>> >> power, or even workload's performance. >>> >> Do anyone have some idea about that? >> > >> > TLB shootdowns are caused by an application in essence, and will indeed >> > cause an impact on power. The most likely culprit is some memory-hungry >> > application(chrome?) forcing pages to be swapped out (or something >> > similar) that were shared between cores, and so each core now needs to >> > update, keeping them out of a deeper C-state. >> > >> > Auke >> > > Thanks~ > I checked memory footprint and found that memory is not bottleneck and > there is not any swap operation during workload running. > But I found some things thru workload profiling. A library > implemented memory management itself and identified two api: > MemoryAllocate() and MemoryFree(). > The following is some call graphs which have something to do with TLB. > > --- flush_tlb_others_ipi > flush_tlb_mm > | > |--88.89%-- unmap_vmas > | unmap_region > | do_munmap > | sys_munmap > | sysenter_do_call > | 0xb77c4424 > | MemoryServices::MemoryFree(void*) > > > | | --50.00%-- flush_tlb_mm > | | zap_page_range > | | sys_madvise > | | sysenter_do_call > | | 0xb77c4424 > | | > MemoryServices::MemoryFree(void*) > > > --20.00%-- flush_tlb_mm > mprotect_fixup > sys_mprotect > sysenter_do_call > 0xb77c4424 > 0xb762910a > __libc_malloc > malloc > MemoryServices::MemoryAllocate(unsigned > int) > > > Do these operations lead to high "TLB shootdowns" interrupt?
probably, sure. _______________________________________________ Power mailing list [email protected] http://www.bughost.org/mailman/listinfo/power
