From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@vger.kernel.org, Patrick McHardy <kaber@trash.net>
Subject: Re: [RFC IPROUTE 00/08]: Time cleanups + nano-second clock resolution support
Date: Tue, 13 Mar 2007 14:42:53 -0700 [thread overview]
Message-ID: <20070313144253.430ef008@freekitty> (raw)
In-Reply-To: <20070304191402.22838.91224.sendpatchset@localhost.localdomain>
On Sun, 4 Mar 2007 20:14:53 +0100 (MET)
Patrick McHardy <kaber@trash.net> wrote:
> This patchset consists of four parts:
>
> - minor TBF time conversion fix
>
> - consolidation of time calculations: consolidate commonly used expressions
> with the goal of making it easier to audit for integer overflows when
> increasing the internally used clock resolution.
>
> - support for detecting the clock resolution used by the kernel and converting
> time values as necessary.
>
> - finally, increase the internally used clock resolution to nano-seconds
>
> These patches have been tested (well, TBF and HFSC) with both old kernels
> and patched kernels using nano-second resolution.
>
>
> tc/m_estimator.c | 4 +--
> tc/m_police.c | 2 -
> tc/q_cbq.c | 15 +++++++------
> tc/q_hfsc.c | 18 +++++++--------
> tc/q_htb.c | 4 +--
> tc/q_netem.c | 14 +++---------
> tc/q_tbf.c | 22 +++++++++----------
> tc/tc_cbq.c | 8 +++----
> tc/tc_core.c | 61 ++++++++++++++++++++++++++++++++++++++----------------
> tc/tc_core.h | 13 +++++++----
> tc/tc_estimator.c | 2 -
> tc/tc_red.c | 2 -
> tc/tc_util.c | 40 ++++++++++++++++++++++-------------
> tc/tc_util.h | 7 +++---
> 14 files changed, 125 insertions(+), 87 deletions(-)
>
> Patrick McHardy:
> [IPROUTE]: tbf: fix latency printing
> [IPROUTE]: Use tc_calc_xmittime() where appropriate
> [IPROUTE]: Introduce tc_calc_xmitsize and use where appropriate
> [IPROUTE]: Introduce TIME_UNITS_PER_SEC to represent internal clock resolution
> [IPROUTE]: Replace "usec" by "time" in function names
> [IPROUTE]: Add sprint_ticks() function and use in CBQ
> [IPROUTE]: Handle different kernel clock resolutions
> [IPROUTE]: Increase internal clock resolution to nsec
applied all
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-03-13 21:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 19:14 [RFC IPROUTE 00/08]: Time cleanups + nano-second clock resolution support Patrick McHardy
2007-03-04 19:14 ` [RFC IPROUTE 01/08]: tbf: fix latency printing Patrick McHardy
2007-03-04 19:14 ` [RFC IPROUTE 02/08]: Use tc_calc_xmittime() where appropriate Patrick McHardy
2007-03-04 19:14 ` [RFC IPROUTE 03/08]: Introduce tc_calc_xmitsize and use " Patrick McHardy
2007-03-04 19:14 ` [RFC IPROUTE 04/08]: Introduce TIME_UNITS_PER_SEC to represent internal clock resolution Patrick McHardy
2007-03-04 19:15 ` [RFC IPROUTE 05/08]: Replace "usec" by "time" in function names Patrick McHardy
2007-03-04 19:15 ` [RFC IPROUTE 06/08]: Add sprint_ticks() function and use in CBQ Patrick McHardy
2007-03-04 19:15 ` [RFC IPROUTE 07/08]: Handle different kernel clock resolutions Patrick McHardy
2007-03-04 19:15 ` [RFC IPROUTE 08/08]: Increase internal clock resolution to nsec Patrick McHardy
2007-03-13 21:42 ` Stephen Hemminger [this message]
2007-03-14 8:54 ` [RFC IPROUTE 00/08]: Time cleanups + nano-second clock resolution support Patrick McHardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070313144253.430ef008@freekitty \
--to=shemminger@linux-foundation.org \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).