netdev - [RFC NET_SCHED 00/03]: ktime + nano-second clock resolution for packet schedulers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sun,  4 Mar 2007 20:05:30 +0100 (MET)
From:	Patrick McHardy <kaber@...sh.net>
To:	netdev@...r.kernel.org
Cc:	Patrick McHardy <kaber@...sh.net>, shemminger@...ux-foundation.org
Subject: [RFC NET_SCHED 00/03]: ktime + nano-second clock resolution for packet schedulers

These patches convert the GETTIMEOFDAY packet scheduler clock source to
ktime (based on Stephen's patch) and add support for using nano-second
clock resolution. I chose a scalar time representation within the packet
schedulers instead of ktime_t since it minimizes the ktime_to_ns() calls
in most cases, it allows to clean up pkt_sched.h quite a bit and HFSC
needs it anyway.

Unlike my previous attempt at this, these patches keep old iproute
versions working with nano-second resolution with the exception of HFSC.
I'm not sure what to do about HFSC yet, so just RFC for now.

 include/linux/jiffies.h |    2 
 include/net/pkt_sched.h |  141 ++++++++++--------------------------------------
 kernel/hrtimer.c        |    1 
 kernel/time.c           |   26 ++++++++
 net/sched/Kconfig       |   17 +++++
 net/sched/sch_api.c     |   11 ++-
 net/sched/sch_hfsc.c    |   37 +++++-------
 7 files changed, 100 insertions(+), 135 deletions(-)

Patrick McHardy:
      [TIME]: Add jiffies_to_nsecs/nsecs_to_jiffies
      [NET_SCHED]: Replace gettimeofday clocksource by ktime
      [NET_SCHED]: Add support for nano-second clock resolution
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html