Lines Matching full:could

16 called ``kdamond``.  Multiple kdamonds could run in parallel, for different
89 mapping is not strictly required but could even incur a high overhead in some
121 bit(s) set again after one sampling period.  This could disturb other kernel
214 access pattern of a region has maintained.  That could be used for good
216 utilizing both the frequency and the recency could be implemented using that.
227 The monitoring target address range could dynamically changed.  For example,
228 virtual memory could be dynamically mapped and unmapped.  Physical memory could
231 As the changes could be quite frequent in some cases, DAMON allows the
257 operation changes for the regions.  The changes could be made by modifying or
259 reconfiguring the hardware.  Both offline and online approaches could be
264 could impose unnecessary redundancy and inefficiency.  The profiling could be
267 spaces could be inefficient.
320 DAMOS upper-bound overhead control feature.  DAMOS could incur high overhead if
323 action to all pages of the huge region could consume unacceptably large system
324 resources.  Preventing such issues by tuning the access pattern could be
402 self-written programs or have good profiling tools, they could know something
494 could be simplified by removing unnecessary knobs for the specific purpose, and