• Home
  • History
  • Annotate
  • Raw
  • Download
  • only in /freebsd-13-stable/sys/contrib/openzfs/module/zfs/

Lines Matching refs:amount

163  * amount of memory consumed by the arc_buf_ts' data buffers can be seen via the
348 * the requested amount of data to be evicted. For example, by default for
948 * device is less than 1GB, the amount of data l2arc_evict()
949 * evicts is significant compared to the amount of restored L2ARC
2225 * Increment the amount of evictable space in the arc_state_t's refcount.
2266 * Decrement the amount of evictable space in the arc_state_t's refcount.
4431 * simply decrement the amount of data evicted from the MRU.
5036 * Reduce the target size as needed to maintain the amount of free
5039 * target arc_size by the deficit amount plus the fractional
5040 * amount. If free memory is positive but less than the fractional
5041 * amount, reduce by what is needed to hit the fractional amount.
5055 * Determine the amount of memory eligible for eviction contained in the
5063 * circumstances, the total amount of clean data in the mru and mfu
5068 * 1. The sum of the amount of dirty data contained by both the mru and
5071 * (i.e. amount of dirty data >= arc_c_min)
5075 * to the amount of dirty data, which is greater than arc_c_min.
5077 * 2. The sum of the amount of dirty data contained by both the mru and
5080 * (i.e. arc_c_min > amount of dirty data)
5083 * (i.e. arc_size >= arc_c_min > amount of dirty data)
5087 * to keep arc_size above arc_c_min. Thus, the maximum amount of
5092 * (i.e. arc_c_min > arc_size > amount of dirty data)
5189 * accomplishes both goals. The maximum amount we could run over by is
5227 * Wait for the specified amount of data (in bytes) to be evicted from the
5234 arc_wait_for_eviction(uint64_t amount)
5241 if (amount != 0) {
5259 MAX(last_count, arc_evict_count) + amount;
5266 uint64_t, amount,
7194 * Throttle writes when the amount of dirty data in the cache
7682 * Calculate maximum amount of dirty data per pool.
7963 * incurring a large amount of I/O round-trip latency. Having two lists
9546 * depends on the amount of its log entries. We always write log blocks
9550 * is less than that, we reduce the amount of committed and restored
10190 * since we may allocate significant amount of memory here, let ARC