From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 4/25]: Cheaper & smaller timestamping
Date: Mon, 02 Apr 2007 08:26:26 +0000 [thread overview]
Message-ID: <200704020926.26151@strip-the-willow> (raw)
In-Reply-To: <200703211844.22972@strip-the-willow>
| > [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.
| - we should be looking at using the new ktime as monotonic but that
| can be a task for another time.
Excellent idea, this may allow to make CCID3 more precise.
By sheer magic, skb_get_timestamp does this already, as I just saw:
static inline void skb_get_timestamp(const struct sk_buff *skb, struct timeval *stamp)
{
*stamp = ktime_to_timeval(skb->tstamp);
}
so we only need to replace the do_gettimeofday() at some time.
I have another idea with regard to timestamps: the field
dccp_inetconnection.icsk_ack.lrcvtime
takes an __u32 timestamp - we could use this for the DCCP timestamp/timestamp echos,
which are 4 bytes (currently this is done for initial SYN RTT).
next prev parent reply other threads:[~2007-04-02 8:26 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 [this message]
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
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=200704020926.26151@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.