netdev - Re: [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 linux-cve-announce PHC
Open Source and information security mailing list archives

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

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

Message-Id: <20070304.162557.112625456.davem@davemloft.net>
Date:	Sun, 04 Mar 2007 16:25:57 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	kaber@...sh.net
Cc:	netdev@...r.kernel.org, shemminger@...ux-foundation.org
Subject: Re: [RFC NET_SCHED 00/03]: ktime + nano-second clock resolution
 for packet schedulers

From: Patrick McHardy <kaber@...sh.net>
Date: Sun,  4 Mar 2007 20:05:30 +0100 (MET)

> 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.

This looks great to me.

Frankly, I think now that we have ktime and all of the proper generic
infrastructure to do this stuff properly, I think we should just use
ktime for the packet scheduler across the board and just delete all of
that old by-hand timekeeping selection crap from pkt_sched.h
-
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