From: Stephen Hemminger <shemminger@linux-foundation.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: Joe Perches <joe@perches.com>, David Miller <davem@davemloft.net>,
Netdev <netdev@vger.kernel.org>
Subject: Re: TCP event tracking via netlink...
Date: Wed, 5 Dec 2007 21:06:49 -0700 [thread overview]
Message-ID: <20071205210649.5a3d1a52@shemminger-laptop> (raw)
In-Reply-To: <Pine.LNX.4.64.0712052336240.9572@kivilampi-30.cs.helsinki.fi>
On Thu, 6 Dec 2007 00:15:49 +0200 (EET)
"Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi> wrote:
> On Wed, 5 Dec 2007, Stephen Hemminger wrote:
>
> > On Wed, 05 Dec 2007 08:53:07 -0800
> > Joe Perches <joe@perches.com> wrote:
> >
> > > > it occurred to me that we might want to do something
> > > > like a state change event generator.
> > >
> > > This could be a basis for an interesting TCP
> > > performance tester.
> >
> > That is what tcpprobe does but it isn't detailed enough to address SACK
> > issues.
>
> ...It would be nice if that could be generalized so that the probe could
> be attached to some other functions than tcp_rcv_established instead.
>
> If we convert remaining functions that don't have sk or tp as first
> argument so that sk is listed first (should be many with wrong ordering
> if any), then maybe a generic handler could be of type:
>
> jtcp_entry(struct sock *sk, ...)
>
> or when available:
>
> jtcp_entry(struct sock *sk, struct sk_buff *ack, ...)
>
>
> --
> i.
An earlier version had hooks in send as well, it is trivial to extend. as long as
the prototypes match, any function arg ordering is okay.
next prev parent reply other threads:[~2007-12-06 4:08 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
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 [this message]
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=20071205210649.5a3d1a52@shemminger-laptop \
--to=shemminger@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=joe@perches.com \
--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