search for: dtlb

...the output. We may want to consider a nontemporal memcpy to at least avoid polluting the cache. These misses contend on the DRAM bus (although currently it may be underutilized and so adding more parallelism will help to keep it busy, but only up to a point). https://reviews.llvm.org/P7947 --event=dTLB-load-misses These are dTLB misses for loads (on my machine, it corresponds to any time that the hardware page table walker kicks in: https://github.com/torvalds/linux/blob/f92b7604149a55cb601fc0b52911b1e11f0f2514/arch/x86/events/intel/core.c#L434 ). Here we also see the getVA codepath (which is bas...

...unters are very useful. Regards, Alastair. -------------- next part -------------- /usr/sbin/perf stat -e cycles -e instructions -e cache-references -e cache-misses -e branch-instructions -e branch-misses -e L1-dcache-loads -e L1-dcache-load-misses -e L1-dcache-stores -e L1-dcache-store-misses -e dTLB-loads -e dTLB-load-misses xz -9e dictionary Performance counter stats for 'xz -9e dictionary': 2,838,843,997 cycles # 0.000 GHz [24.96%] 3,017,892,661 instructions # 1.06 insns per cycle [33.31%] 28,281,...

Hi, @Alastair: Thanks a bunch for explaining this so well. I was able to write a simple profiler, and run it. I need to profile the code for branches (branch mis predicts simulation), load/store instructions (for cache hits/miss rate), and a couple of other things and therefore, would need to instrument the code. However, I would like to know if writing the output to a file would increase the

...wrote: >> >> Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> writes: >>> This will also greatly facilitate certain measurements I'd like to do >>> w.r.t. different strategies for avoiding memory costs for input files (esp. >>> minor faults and dTLB costs). I've almost gotten to the point of >>> implementing this just to do those measurements. >> >> If you do please keep it local. The bare minimum we have of library >> support is already disproportionately painful and prevents easier sharing >> with COFF....

...t lists.llvm.org> wrote: > > Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> writes: >> This will also greatly facilitate certain measurements I'd like to do >> w.r.t. different strategies for avoiding memory costs for input files (esp. >> minor faults and dTLB costs). I've almost gotten to the point of >> implementing this just to do those measurements. > > If you do please keep it local. The bare minimum we have of library > support is already disproportionately painful and prevents easier sharing > with COFF. We should really not...

...>>> Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> writes: >>>> This will also greatly facilitate certain measurements I'd like to do >>>> w.r.t. different strategies for avoiding memory costs for input files (esp. >>>> minor faults and dTLB costs). I've almost gotten to the point of >>>> implementing this just to do those measurements. >>> >>> If you do please keep it local. The bare minimum we have of library >>> support is already disproportionately painful and prevents easier sharing >...

Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> writes: > This will also greatly facilitate certain measurements I'd like to do > w.r.t. different strategies for avoiding memory costs for input files (esp. > minor faults and dTLB costs). I've almost gotten to the point of > implementing this just to do those measurements. If you do please keep it local. The bare minimum we have of library support is already disproportionately painful and prevents easier sharing with COFF. We should really not add more until the link...

...that > sense, passing a map from filename to MemoryBuffer objects in addition to > command line arguments is fine to me. > This will also greatly facilitate certain measurements I'd like to do w.r.t. different strategies for avoiding memory costs for input files (esp. minor faults and dTLB costs). I've almost gotten to the point of implementing this just to do those measurements. -- Sean Silva > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev &...

...t; Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> writes: >>>>> This will also greatly facilitate certain measurements I'd like to do >>>>> w.r.t. different strategies for avoiding memory costs for input files (esp. >>>>> minor faults and dTLB costs). I've almost gotten to the point of >>>>> implementing this just to do those measurements. >>>> >>>> If you do please keep it local. The bare minimum we have of library >>>> support is already disproportionately painful and prevents eas...

...m-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> writes: > >> This will also greatly facilitate certain measurements I'd like to do > >> w.r.t. different strategies for avoiding memory costs for input files (esp. > >> minor faults and dTLB costs). I've almost gotten to the point of > >> implementing this just to do those measurements. > > > > If you do please keep it local. The bare minimum we have of library > > support is already disproportionately painful and prevents easier sharing > > with CO...

...s: > >>>>> This will also greatly facilitate certain measurements I'd like > >>>>> to do > >>>>> w.r.t. different strategies for avoiding memory costs for input > >>>>> files (esp. > >>>>> minor faults and dTLB costs). I've almost gotten to the point > >>>>> of > >>>>> implementing this just to do those measurements. > >>>> > >>>> If you do please keep it local. The bare minimum we have of > >>>> library > >>&gt...

...gt; > > > Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> writes: > >> This will also greatly facilitate certain measurements I'd like to do > >> w.r.t. different strategies for avoiding memory costs for input files > (esp. > >> minor faults and dTLB costs). I've almost gotten to the point of > >> implementing this just to do those measurements. > > > > If you do please keep it local. The bare minimum we have of library > > support is already disproportionately painful and prevents easier sharing > > with CO...

...>> This will also greatly facilitate certain measurements I'd like > > >>>>> to do > > >>>>> w.r.t. different strategies for avoiding memory costs for input > > >>>>> files (esp. > > >>>>> minor faults and dTLB costs). I've almost gotten to the point > > >>>>> of > > >>>>> implementing this just to do those measurements. > > >>>> > > >>>> If you do please keep it local. The bare minimum we have of > > >>>>...

...t; Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> writes: >> >> This will also greatly facilitate certain measurements I'd like to do >> >> w.r.t. different strategies for avoiding memory costs for input files >> (esp. >> >> minor faults and dTLB costs). I've almost gotten to the point of >> >> implementing this just to do those measurements. >> > >> > If you do please keep it local. The bare minimum we have of library >> > support is already disproportionately painful and prevents easier >>...

...vm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> writes: >> >> This will also greatly facilitate certain measurements I'd like to do >> >> w.r.t. different strategies for avoiding memory costs for input files (esp. >> >> minor faults and dTLB costs). I've almost gotten to the point of >> >> implementing this just to do those measurements. >> > >> > If you do please keep it local. The bare minimum we have of library >> > support is already disproportionately painful and prevents easier sharing &...

...a llvm-dev <llvm-dev at lists.llvm.org> writes: >>> >> This will also greatly facilitate certain measurements I'd like to do >>> >> w.r.t. different strategies for avoiding memory costs for input files >>> (esp. >>> >> minor faults and dTLB costs). I've almost gotten to the point of >>> >> implementing this just to do those measurements. >>> > >>> > If you do please keep it local. The bare minimum we have of library >>> > support is already disproportionately painful and prevents...

...t; Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> writes: >> >> This will also greatly facilitate certain measurements I'd like to do >> >> w.r.t. different strategies for avoiding memory costs for input files >> (esp. >> >> minor faults and dTLB costs). I've almost gotten to the point of >> >> implementing this just to do those measurements. >> > >> > If you do please keep it local. The bare minimum we have of library >> > support is already disproportionately painful and prevents easier >>...

...sts.llvm.org <mailto:llvm-dev at lists.llvm.org>> writes: >>> >> This will also greatly facilitate certain measurements I'd like to do >>> >> w.r.t. different strategies for avoiding memory costs for input files (esp. >>> >> minor faults and dTLB costs). I've almost gotten to the point of >>> >> implementing this just to do those measurements. >>> > >>> > If you do please keep it local. The bare minimum we have of library >>> > support is already disproportionately painful and prevents...

...lvm-dev at lists.llvm.org> writes: >>>> >> This will also greatly facilitate certain measurements I'd like to do >>>> >> w.r.t. different strategies for avoiding memory costs for input >>>> files (esp. >>>> >> minor faults and dTLB costs). I've almost gotten to the point of >>>> >> implementing this just to do those measurements. >>>> > >>>> > If you do please keep it local. The bare minimum we have of library >>>> > support is already disproportionately painf...

...<llvm-dev at lists.llvm.org> writes: > >>> This will also greatly facilitate certain measurements I'd like > >>> to do > >>> w.r.t. different strategies for avoiding memory costs for input > >>> files (esp. > >>> minor faults and dTLB costs). I've almost gotten to the point of > >>> implementing this just to do those measurements. > >> > >> If you do please keep it local. The bare minimum we have of > >> library > >> support is already disproportionately painful and prevents e...