From: David Miller <davem@davemloft.net>
To: Gavin.McCullagh@nuim.ie
Cc: linux-net@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: reading the tcp headers within the write queue
Date: Thu, 13 Dec 2007 11:00:50 -0800 (PST) [thread overview]
Message-ID: <20071213.110050.104716141.davem@davemloft.net> (raw)
In-Reply-To: <20071213185626.GV7409@nuim.ie>
From: Gavin McCullagh <Gavin.McCullagh@nuim.ie>
Date: Thu, 13 Dec 2007 18:56:26 +0000
> I'm trying to hack together something which will run through the
> retransmit queue looking at the tcp headers.
The packets in the retransmit queue are headerless, the
header only gets added to clones of the retransmit queue
frames during the actual transmit.
And this question belongs on netdev not linux-net.
next parent reply other threads:[~2007-12-13 19:00 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 ` David Miller [this message]
2007-12-13 19:08 ` reading the tcp headers within the write queue Gavin McCullagh
2007-12-13 19:13 ` 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=20071213.110050.104716141.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Gavin.McCullagh@nuim.ie \
--cc=linux-net@vger.kernel.org \
--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).