Mike, > Every aggregating function has to have a defined, fixed type, that determines > how its implementation in kernel and userland, a portion of which is quoted > above, performs the underlying arithmetic. Since our original release, the > type signatures of the aggregating functions to which you are referring > have their signature as: sum(uint64_t arg), and so on.
As Bryan mentioned earlier, quantize()/lquantize() also treat their arguments as uint64_t but in the kernel implementation convert it to int64_t. Can the same thing be done for max()/min()/avg()? - akolb _______________________________________________ dtrace-discuss mailing list [email protected]
