Lines Matching full:could

16 called ``kdamond``.  Multiple kdamonds could run in parallel, for different
99 mapping is not strictly required but could even incur a high overhead in some
131 bit(s) set again after one sampling period.  This could disturb other kernel
240 access pattern of a region has maintained.  That could be used for good
242 utilizing both the frequency and the recency could be implemented using that.
253 The monitoring target address range could dynamically changed.  For example,
254 virtual memory could be dynamically mapped and unmapped.  Physical memory could
257 As the changes could be quite frequent in some cases, DAMON allows the
288 time scale of the given purpose.  This could happen if the workload is actually
294 monitoring results show zero ``nr_accesses``, regions could still be
343 operation changes for the regions.  The changes could be made by modifying or
345 reconfiguring the hardware.  Both offline and online approaches could be
350 could impose unnecessary redundancy and inefficiency.  The profiling could be
353 spaces could be inefficient.
442 DAMOS upper-bound overhead control feature.  DAMOS could incur high overhead if
445 action to all pages of the huge region could consume unacceptably large system
446 resources.  Preventing such issues by tuning the access pattern could be
508 - ``user_input``: User-provided value.  Users could use any metric that they
511   time (PSI) could be examples.  Note that users should explicitly set
556 self-written programs or have good profiling tools, they could know something
649 <damon_design_damos_filters>` that handled on core logic could affect this.
738 could be simplified by removing unnecessary knobs for the specific purpose, and