Lines Matching refs:each
124 Below four sections describe each of the DAMON core mechanisms and the five
136 access to each page per ``sampling interval`` and aggregates the results. In
137 other words, counts the number of the accesses to each page. After each
163 one page in the region is required to be checked. Thus, for each ``sampling
164 interval``, DAMON randomly picks one page in each region, waits for one
181 adaptively merges and splits each region based on their access frequency.
183 For each ``aggregation interval``, it compares the access frequencies of
185 after it reports and clears the aggregated access frequency of each region, it
186 splits each region into two or three regions if the total number of regions
201 yet another counter called ``age`` in each region. For each ``aggregation
217 abstracted monitoring target memory area only for each of a user-specified time
271 each action is in the DAMON operations set layer because the implementation
326 The prioritization mechanism should be different for each action. For example,
329 page collapse scheme action. Hence, the prioritization mechanisms for each
330 action are implemented in each DAMON operations set, together with the actions.
337 to specify the weight of each access pattern property and passes the
379 number of filters for each scheme. Each filter specifies the type of target
420 implemented by each DAMON API user kernel components, instead. DAMON subsystem
461 in runtime. For each special-purpose system-wide data access-aware system