Searched refs:percentage (Results 1 – 11 of 11) sorted by relevance
93 int percentage; in util_compute_percentage_charge() local101 percentage = ((double) chargeLevel / (double) chargeLastFull) * 100; in util_compute_percentage_charge()107 if (percentage > 100) { in util_compute_percentage_charge()108 HAL_WARNING (("Percentage %i, returning 100!", percentage)); in util_compute_percentage_charge()112 if (percentage < 0) { in util_compute_percentage_charge()113 HAL_WARNING (("Percentage %i, returning -1!", percentage)); in util_compute_percentage_charge()116 return percentage; in util_compute_percentage_charge()
17 # Return 0 if the percentage difference between $a and $b is $percent or18 # greater. Return 1 if the percentage is lower or if we would divide by21 # Do $action if the calculated percentage is greater or equal to that passed in:23 # Do $action if the calculated percentage is less than that passed in:
285 future use. The percentage at the right is the number of freelist pages291 always 1. The percentage at the right is the number of header pages320 counted when computing this number. The percentage at the right shows327 percentage at the right is the user data size divided by the total file350 data. The percentage at the right is the bytes of payload divided by357 that are stored with the data. The percentage at the right is the bytes362 The sum of the sizes of all keys under this category. The percentage at404 percentage at the right is the number of unused bytes divided by the410 percentage at the right is the number of unused bytes divided by the416 pages. The percentage at the right is the number of unused bytes
116 int percentage; in analyze() local177 percentage = (est_deletes * 100) / (total_files ? total_files : 1); in analyze()178 if (est_deletes >= CONFIRM_MIN && percentage >= CONFIRM_PCT) in analyze()
3 % the percentage of the total running time of the
10 %time the percentage of the total time of the program
105 and comparing it to a specified percentage. This comparision is always 111 entries as regards to aging but is absolute - i.e. no percentage governs 114 2.3.2 The percentage and additional aging count are adjustable by the 124 There are three sleep times and two percentage levels specifiable by the
403 int64_t percentage; in ckfini() local435 percentage = diskreads * 100 / totalreads; in ckfini()437 percentage = 0; in ckfini()441 (longlong_t)percentage); in ckfini()
595 * Below rules are so we get a single suspect list in 1 fault with percentage
16938 percentage
16936 percentage