Lines Matching full:much

28  *   1) space_info.  This is the ultimate arbiter of how much space we can use.
38  *   much space is accounted for in space_info->bytes_may_use.
119  *     Look at the delalloc comment to get an idea of how much space is reserved
462 	 * overcommit much, and if we're very close to full it'll keep us from  in calc_available_free_space()
473 	 * too much, let it overcommit up to 1/8 of the space.  in calc_available_free_space()
484 	 * will over-commit too much leading to ENOSPC. Align down to the  in calc_available_free_space()
695 		 * to_reclaim is set to however much metadata we need to  in shrink_delalloc()
696 		 * reclaim, but reclaiming that much data doesn't really track  in shrink_delalloc()
992 	 * much delalloc we need for the background flusher to kick in.  in need_preemptive_reclaim()
1215  * This is for normal flushers, it can wait as much time as needed. We will
1237  * much we need to flush, instead it attempts to keep us below the 80% full
1290 		 * We really want to avoid flushing delalloc too much, as it  in btrfs_preempt_reclaim_metadata_space()
1620  * @flush:      how much we can flush
1996  * utilization when near full, and not do too much reclaim while
2017  * Furthermore, we want to avoid doing too much reclaim even if there are good