From: Eric Dumazet <eric.dumazet@gmail.com>
To: Anatoly Sivov <mm05@mail.ru>
Cc: netdev@vger.kernel.org
Subject: Re: why does skb->tstamp use getnstimeofday?
Date: Sun, 15 Jan 2012 19:56:53 +0100 [thread overview]
Message-ID: <1326653813.5287.84.camel@edumazet-laptop> (raw)
In-Reply-To: <op.v74z14g2fzo5me@stalin>
Le dimanche 15 janvier 2012 à 21:55 +0400, Anatoly Sivov a écrit :
> I missed that field tstamp is used for things other than RTT and can be
> even user-spaced with SO_TIMESTAMP.
> However, timekeeper speed up/slow down (due to ntp) can seriously affect
> some congestion avoidance algorithm quality, I guess.
> Am I wrong?
For what kind of application or protocol do you feel there could be a
problem ?
TCP stack doesnt use skb->tstamp/jtime_t, for example, but jiffies.
ntp adjustements are normally very small and nobody notice.
next prev parent reply other threads:[~2012-01-15 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 15:11 why does skb->tstamp use getnstimeofday? Anatoly Sivov
2012-01-15 16:42 ` Eric Dumazet
2012-01-15 17:55 ` Anatoly Sivov
2012-01-15 18:00 ` Anatoly Sivov
2012-01-15 18:56 ` Eric Dumazet [this message]
2012-01-15 19:55 ` Anatoly Sivov
2012-01-16 22:05 ` Rick Jones
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=1326653813.5287.84.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=mm05@mail.ru \
--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