Re: [PATCH rt-tests] queuelat: use ARM implementation of gettick also for all !x86 archs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 2019-12-12 18:46, Sebastian Andrzej Siewior wrote:
So what I select as frequency for the !x86 case? And why.

IMO, an user should be able to run rt-tests without the need to provide special configuration or tuning. queuelat is a bit hard to use at this point.

That freq. script reports here:
|1555.184 1566.269 1566.498 1560.055 1593.149 1568.185 1583.807 1599.096 2574.546 2572.408 2573.849 2583.862 2619.402 1825.680 1847.264 1870.318 2552.102 1570.552 1589.650 1595.813 1590.253 1573.834 1589.438 1599.439 1770.963 1786.370 1814.918 1811.936 1828.277 1850.905 1861.976 1792.809

I guess I pick one…

Could someone please figure out the actual difference of clock_gettime()
vs rdtsc() so we know how important it is.

I didn't really understood what the test is doing. The initial clock_gettime() patch was just to shoutup the compiler.

Thanks,
Daniel



[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux