Lines Matching full:aggregation
400 * aggregation in the postmortem case (some modules may in dt_aggregate_mod()
401 * appear more than once in aggregation output). It seems in dt_aggregate_mod()
960 * If we're here, the values for the two aggregation elements are
1103 * Use the aggregation buffer size as reloaded from the kernel.
1322 * If we need to deliver per-aggregation totals, we're going to take
1324 * determine our maximum aggregation ID, one to actually total
1466 * of the aggregation when aggpack is set.
1694 * If the sorting position is greater than the number of aggregation
1701 * First we need to translate the specified aggregation variable IDs
1702 * into a linear map that will allow us to translate an aggregation
1732 * We have an aggregation variable that is present
1733 * more than once in the array of aggregation
1737 * position from which this aggregation variable
1751 * for the sort position yields the same aggregation
1767 * used to properly format a zero-valued aggregation.
1794 * zero-filled data. This will occur if an aggregation variable that
1798 * aggregation, but without any record description, we don't know the
1799 * aggregating action that corresponds to the aggregation variable. To
1800 * try to find a match, we're simply going to lookup aggregation IDs
1802 * for the specified aggregation variable ID. If we find a match,
1803 * we'll use that. If we iterate over all aggregation IDs and don't
1805 * enablings can't currently derive either aggregation variable IDs or
1806 * aggregation variable names given only an aggregation ID.) In this
1807 * obscure case (anonymous enabling, multiple aggregation printa() with
1810 * aggregation variable that contains any non-zero value.
1850 * We couldn't find this aggregation, meaning
1856 * first non-zero aggregation -- of which, of
1923 * manually dig it out of the aggregation
2038 * Before we assume that this aggregation variable
2043 * aggregation variable that isn't present for this
2044 * key; in this case, the aggregation data that we