From: Aaron Isotton <aaron@isotton.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Dump the tcp_sock structure for every packet
Date: Sun, 28 May 2006 19:49:57 +0200 [thread overview]
Message-ID: <4479E2C5.90708@isotton.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
Hi,
I'm doing some kernel hacking to evaluate different TCP congestion
control algorithms in a WLAN mesh network.
I need to output some TCP parameters (such as window sizes et al) over
time; what I'd wish to do is outputting them to a character device
whenever a packet comes in/is sent.
I've written the device code, now I just need to output the parameters
using that device. The easiest way would be simply outputting the whole
tcp_sock structure to the device, and then reading it in from user space.
The problem is that I don't know where exactly in the TCP implementation
the packets are transmitted/received, i.e. where I should send the data
over to the device implementation.
The ideal case would of course be some kind of callback/hook function; I
imagine there might be something like this for the netfilter modules,
but I have no idea.
Can anybody help me with this?
Thank you,
Aaron
--
Aaron Isotton | http://www.isotton.com/
I'll give you a definite maybe. --Samuel Goldwyn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next reply other threads:[~2006-05-28 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 17:49 Aaron Isotton [this message]
[not found] ` <447AF09F.705@gmail.com>
2006-05-29 13:58 ` Dump the tcp_sock structure for every packet Aaron Isotton
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=4479E2C5.90708@isotton.com \
--to=aaron@isotton.com \
--cc=linux-kernel@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