From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 4/25]: Cheaper & smaller timestamping
Date: Fri, 13 Apr 2007 12:19:31 +0000 [thread overview]
Message-ID: <200704131319.31362@strip-the-willow> (raw)
In-Reply-To: <200703211844.22972@strip-the-willow>
Quoting Arnaldo Carvalho de Melo:
| On 4/2/07, Gerrit Renker <gerrit@erg.abdn.ac.uk> wrote:
| > | > [DCCP]: Cheaper & smaller timestamping
| >
| > | A couple of comments though:
| > | - this is how I had the code originally in many cases and Arnaldo
| > | changed - can't remember why.
| > Arnaldo's code uses a reference point, the skb_get_timestamp() also did
| > that. May be useful against old incarnations across reboots.
|
| I got to this cset now in today's merge session, the cset that did that was:
|
| b0e567806d16586629468c824dfb2e71155df7da
|
| Comment was, unfortunately, not so clear:
|
| ----
| [acme@mica net-2.6.22]$ git-show b0e567806d16586629468c824dfb2e71155df7da
| commit b0e567806d16586629468c824dfb2e71155df7da
| Author: Arnaldo Carvalho de Melo <acme@mandriva.com>
| Date: Fri Sep 9 02:38:35 2005 -0300
|
| [DCCP] Introduce dccp_timestamp
|
| To start the timestamps with 0.0ms, easing the integer maths in
| the CCIDs, this
| probably will be reworked to use the to be introduced struct timeval_offset
| infrastructure out of skb_get_timestamp, etc.
|
| Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
| ---
|
| What are the architectures you've been testing? All 64 bits? IIRC the
| problem was related to overflows, suseconds_t is unsigned long, so 32
| bits on i386...
I have tested on various i386 instances (where it is `long') and on sparc64 (where it is `int', as
in parisc). I was just calculating - there is indeed a chance to produce overflow, since we add
in timeval_add_usecs (since it is a signed type, the same problem seems to reappear in timeval_sub_usecs).
I don't have accurate figures at the moment with regard to overflow, but I assume that it is better to revert
this patch?
There is a related question - with the new timesystem, should we convert to __get_realtime_clock_ts(), as
the comment above do_gettimeofday() says in kernel/timer.c ?
I would be glad for clarification, since there are quite a few patches to update.
Cheers.
next prev parent reply other threads:[~2007-04-13 12:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 18:44 [PATCH 4/25]: Cheaper & smaller timestamping Gerrit Renker
2007-03-26 2:41 ` Ian McDonald
2007-04-02 8:26 ` Gerrit Renker
2007-04-12 14:14 ` Arnaldo Carvalho de Melo
2007-04-12 14:28 ` Arnaldo Carvalho de Melo
2007-04-13 12:19 ` Gerrit Renker [this message]
2007-04-13 12:35 ` Arnaldo Carvalho de Melo
2007-04-13 12:49 ` Gerrit Renker
2007-04-13 13:05 ` Arnaldo Carvalho de Melo
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=200704131319.31362@strip-the-willow \
--to=gerrit@erg.abdn.ac.uk \
--cc=dccp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.