From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: David Miller <davem@davemloft.net>
Cc: jheffner@psc.edu, ilpo.jarvinen@helsinki.fi, netdev@vger.kernel.org
Subject: Re: TCP event tracking via netlink...
Date: Thu, 6 Dec 2007 13:58:24 +0300 [thread overview]
Message-ID: <20071206105823.GA19472@2ka.mipt.ru> (raw)
In-Reply-To: <20071205.210343.57693750.davem@davemloft.net>
On Wed, Dec 05, 2007 at 09:03:43PM -0800, David Miller (davem@davemloft.net) wrote:
> I think this work is very different.
>
> When I say "state" I mean something more significant than
> CLOSE, ESTABLISHED, etc. which is what Samir's patches are
> tracking.
>
> I'm talking about all of the sequence numbers, SACK information,
> congestion control knobs, etc. whose values are nearly impossible to
> track on a packet to packet basis in order to diagnose problems.
I pointed that work as a possible basis for collecting more info if you
needs including sequence numbers, window sizes and so on.
It just requires a useful structure layout placed, so that one would not
require to recreate the same bits again, so that it could be called from
any place inside the stack.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2007-12-06 10:58 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 [this message]
2007-12-06 5:00 ` David Miller
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=20071206105823.GA19472@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.