From: David Miller <davem@davemloft.net>
To: oakad@yahoo.com
Cc: netdev@vger.kernel.org
Subject: Re: Bad TCP timestamps on non-PC platforms
Date: Thu, 06 Jan 2011 08:44:33 -0800 (PST) [thread overview]
Message-ID: <20110106.084433.193708782.davem@davemloft.net> (raw)
In-Reply-To: <219643.83181.qm@web37604.mail.mud.yahoo.com>
From: Alex Dubov <oakad@yahoo.com>
Date: Wed, 5 Jan 2011 22:55:43 -0800 (PST)
> On embedded platforms, where real time clock is initialized lately or
> absent outright, this causes TSval field of outgoing TCP packets to be
> set to some garbage value, in my case in the vicinity of 0xffffffff.
The TCP timestamp is set from "jiffies", not from the RTC clock.
next prev parent reply other threads:[~2011-01-06 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 6:55 Bad TCP timestamps on non-PC platforms Alex Dubov
2011-01-06 8:09 ` Eric Dumazet
2011-01-07 1:55 ` Alex Dubov
2011-01-07 2:11 ` Eric Dumazet
2011-01-07 6:39 ` Alex Dubov
2011-01-06 16:44 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-10 3:41 Alex Dubov
2011-01-10 3:57 ` Stephen Hemminger
2011-01-10 6:33 ` Alex Dubov
2011-01-10 7:07 ` Eric Dumazet
2011-01-10 7:19 ` David Miller
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=20110106.084433.193708782.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=oakad@yahoo.com \
/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).