netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jheffner@psc.edu
Cc: ilpo.jarvinen@helsinki.fi, netdev@vger.kernel.org
Subject: Re: TCP event tracking via netlink...
Date: Wed, 05 Dec 2007 21:00:50 -0800 (PST)	[thread overview]
Message-ID: <20071205.210050.86277995.davem@davemloft.net> (raw)
In-Reply-To: <4756B175.5010108@psc.edu>

From: John Heffner <jheffner@psc.edu>
Date: Wed, 05 Dec 2007 09:11:01 -0500

> FWIW, sounds similar to what these guys are doing with SIFTR for FreeBSD:
> http://caia.swin.edu.au/urp/newtcp/tools.html
> http://caia.swin.edu.au/reports/070824A/CAIA-TR-070824A.pdf

Yes, my proposal is very similar to this SIFTR work.

In their work they tap into the stack using the packet filtering
hooks.

In this way they avoid having to make TCP stack modifications, they
just look up the PCB and dump state, whereas we have more liberty to
do more serious surgery :-)

  parent reply	other threads:[~2007-12-06  5:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-05 13:30 TCP event tracking via netlink David Miller
2007-12-05 14:11 ` John Heffner
2007-12-05 14:48   ` Evgeniy Polyakov
2007-12-05 15:12     ` Samir Bellabes
2007-12-06  5:03     ` David Miller
2007-12-06 10:58       ` Evgeniy Polyakov
2007-12-06  5:00   ` David Miller [this message]
2007-12-05 16:53 ` Joe Perches
2007-12-05 21:33   ` Stephen Hemminger
2007-12-05 22:15     ` Ilpo Järvinen
2007-12-06  4:06       ` Stephen Hemminger
2007-12-06 10:20     ` David Miller
2007-12-06 13:28       ` Arnaldo Carvalho de Melo
2007-12-05 23:18 ` Ilpo Järvinen
2007-12-06 10:33   ` David Miller
2007-12-06 17:23     ` Stephen Hemminger
2007-12-07  6:51       ` David Miller
2008-01-02  8:22       ` David Miller
2008-01-02 11:05         ` Ilpo Järvinen
2008-01-03  9:26           ` David Miller
2007-12-07 16:43     ` Ilpo Järvinen

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=20071205.210050.86277995.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=jheffner@psc.edu \
    --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).