* iproute2 and kernel clock resolutions
@ 2015-01-21 13:22 Ignacy Gawedzki
0 siblings, 0 replies; only message in thread
From: Ignacy Gawedzki @ 2015-01-21 13:22 UTC (permalink / raw)
To: netdev; +Cc: Patrick McHardy, Stephen Hemminger
Hi,
While reading tc/tc_core.c, I'm having a hard time making sense of what
tc_core_init() is actually supposed to do.
It looks just as if clock_res is not filled with the correct value from
/proc/net/psched, taking into account the "compatibility hack" that follows.
AFAICT from the historical kernel Git repository, the third value in
/proc/net/psched has always been hardcoded as 1000000, so it seems that the
condition clock_res == 1000000000 is always false. Shouldn't clock_res be
filled with the fourth value instead of the third, by any chance?
Could also anyone explain to me what this hack is actually about?
Thanks,
Ignacy
--
Ignacy Gawędzki
R&D Engineer
Green Communications
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-01-21 13:23 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-01-21 13:22 iproute2 and kernel clock resolutions Ignacy Gawedzki
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox