Lines Matching full:cache

9 False sharing is related with cache mechanism of maintaining the data
10 coherence of one cache line stored in multiple CPU's caches; then
20 Member 'refcount'(A) and 'name'(B) _share_ one cache line like below::
29          | A      B             | Cache 0     | A       B            | Cache 1
44 reload the whole cache line over and over due to the 'sharing', even
49 mm_struct struct, whose cache line layout change triggered a
65 members could be purposely put in the same cache line to make them
66 cache hot and save cacheline/TLB, like a lock and the data protected
75   purposely put in one cache line.
76 * global data being put together in one cache line. Some kernel
78   which can easily be grouped together and put into one cache line.
80   without being noticed (cache line is usually 64 bytes or more),
99 perf-c2c can capture the cache lines with most false sharing hits,
100 decoded functions (line number of file) accessing that cache line,
126 'pahole' decodes data structure layouts delimited in cache line
146 * Separate hot global data in its own dedicated cache line, even if it
148   cache line and TLB entries.
150   - Commit 91b6d3256356 ("net: cache align tcp_memory_allocated, tcp_sockets_allocated")
153   different cache lines.  One downside is it may introduce new false
177   - Commit 520f897a3554 ("ext4: use percpu_counters for extent_status cache hits/misses")
184 * Be aware of cache line boundaries
188   different cache lines.
200 randomization mechanism, which also randomizes the situation of cache