From: David Miller <davem@davemloft.net>
To: Gavin.McCullagh@nuim.ie
Cc: netdev@vger.kernel.org
Subject: Re: reading the tcp headers within the write queue
Date: Thu, 13 Dec 2007 11:13:27 -0800 (PST) [thread overview]
Message-ID: <20071213.111327.160083733.davem@davemloft.net> (raw)
In-Reply-To: <20071213190859.GW7409@nuim.ie>
From: Gavin McCullagh <Gavin.McCullagh@nuim.ie>
Date: Thu, 13 Dec 2007 19:08:59 +0000
> Thought that might be it. I presume there isn't any other residue of the
> tcp options elsewhere, that one could look at when the packet gets
> acknowledged? I'm particularly interested in the timestamp.
Every time we transmit, the timestamp will be different.
We store the jiffies at transmit time in TCP_SKB_CB(skb)->when,
so you can use that. This is the value we use to compute the
timestamp.
prev parent reply other threads:[~2007-12-13 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071213185626.GV7409@nuim.ie>
2007-12-13 19:00 ` reading the tcp headers within the write queue David Miller
2007-12-13 19:08 ` Gavin McCullagh
2007-12-13 19:13 ` David Miller [this message]
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=20071213.111327.160083733.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Gavin.McCullagh@nuim.ie \
--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).