Lines Matching full:flush

45  * more unflushed changes are accounted in memory, we flush a selected group
48  * flush any unflushed changes from memory to disk (i.e. the metaslab's space
74  *   we flush that metaslab.
91  *   reasons. First of all, it is used during flushing where we try to flush
120  *   algorithm (described later) tries to estimate how many metaslabs to flush
126  *   * we modify or pop entries from its head when we flush metaslabs
134  * The decision of how many metaslabs to flush on a give TXG is guided by
143  * unflushed changes are passing that threshold, we flush metaslabs, which
149  * when loading the pool. At the same time we don't want to flush a lot of
156  * many metaslabs we need to flush based on the current rate of incoming blocks
158  * the question of how many metaslabs do we need to flush in order to get rid
166  * metaslabs would we need to flush from now in order to avoid exceeding our
210  * map's block size as we accumulate more changes per flush.
212  * Given that this tunable indirectly controls the flush rate (metaslabs
218  * 1] Assuming a constant flush rate and a constant incoming rate of log blocks
275  * Tunable that sets the lower bound on the metaslabs to flush every TXG.
283  * want to flush more metaslabs than our adaptable heuristic plans to flush.
409  * We typically flush the oldest flushed metaslab so the first (and oldest)
411  * we may flush the second oldest one which may be part of an entry later in
486  * Scenario [3]: At times we decide to flush all the metaslabs in the pool
491  * we flush, entries in the summary are also destroyed. This brings a weird
492  * corner-case when we flush the last metaslab and the log space map of the
626  * we flush to satisfy our block heuristic for the log spacemap
658 	 * our limit and we need to flush.
706 		 * the limit was just exceeded and we flush metaslabs
776 	 * case, it is important to not flush any metaslabs as that
781 	 * we try to flush all the metaslabs for that TXG before
806 	 * This variable tells us how many metaslabs we want to flush based
808 	 * of log space map feature). We also decrement this as we flush
888 	 * not able to flush any metaslabs the current TXG.
899 	 * At this point we tried to flush as many metaslabs as we
900 	 * can as the pool is getting exported. Reset the "flush all"
1101 	 * metaslab's space map, then ignore it. Note that we flush
1406 	"Minimum number of metaslabs to flush per dirty TXG");