Lines Matching defs:histogram

2021 metaslab_aux_histogram_add(uint64_t *histogram, uint64_t shift,
2027 	 * the space map histogram, and not the range tree histogram, as we
2029 	 * from the space map histogram.
2034 		histogram[idx] += rt->rt_histogram[i] << (i - idx - shift);
2048  * wherever the metaslab's space map histogram is updated. This way
2050  * histogram are currently not available for allocations (e.g because
2060 	 * This is similar to the metaslab's space map histogram updates
2118  * with the contents of the histogram (either the range tree's histogram
2897  * by calculating the space in each bucket of the spacemap histogram and
3110 		 * space map's histogram. This allows us to compare loaded
3128  * Calculate the weight based on the on-disk histogram. Should be applied
3142 	 * Create a joint histogram from all the segments that have made
3143 	 * it to the metaslab's space map histogram, that are not yet
3146 	 * these segments from the space map's histogram to get a more
3176  * is determined by highest bucket in the histogram. The information
3315 	 * Segment-based weighting requires space map histogram support.
3533 	 * histogram; calculate the new weight based on that information.
3936 		 * For all histogram operations below refer to the
3962 		 * Since we recreated the histogram (and potentially
4128 	 * Note: metaslab_condense() clears the space map's histogram.
4129 	 * Therefore we must verify and remove this histogram before
4213 		 * histogram in the range tree. This gives us an opportunity
4214 		 * to bring the space map's histogram up-to-date so we clear
4221 		 * Since we've cleared the histogram we need to add back
4223 		 * any deferred space. This allows the on-disk histogram
4232 		 * ensure that we don't end up with a space map histogram
4244 	 * map histogram. We want to make sure that the on-disk histogram
5058 		 * tree histogram) since it contains the space that is