On Mon, Feb 13, 2023 at 02:08:08PM +0800, yang.yang29@xxxxxxxxxx wrote: > From: Wang Yong <wang.yong12@xxxxxxxxxx> > > Improve the average delay precision of getdelay tool to microsecond. > When using the getdelay tool, it is sometimes found that the average > delay except CPU is not 0, but display is 0, because the precison is too > low. For example, see delay average of SWAP below when using ZRAM. > > print delayacct stats ON > PID 32915 > CPU count real total virtual total delay total delay average > 339202 2793871936 9233585504 7951112 0.000ms > IO count delay total delay average > 41 419296904 10ms > SWAP count delay total delay average > 242589 1045792384 0ms > This wrong display is misleading, so improve the millisecond precision > of the average delay to microsecond just like CPU. Then user would > get more accurate information of delay time. I'm kinda confused. 0.000ms is same as 0ms, right? And did you mean accuracy of delay average is to be same as CPU time? -- An old man doll... just what I always wanted! - Clara
Attachment:
signature.asc
Description: PGP signature
