From: Bill Fink <billfink@mindspring•com>
To: David Miller <davem@davemloft•net>
Cc: therbert@google•com, netdev@vger•kernel.org
Subject: Re: [PATCH] tcp: SO_TIMESTAMP implementation for TCP
Date: Sat, 1 May 2010 01:07:35 -0400 [thread overview]
Message-ID: <20100501010735.dfe097bc.billfink@mindspring.com> (raw)
In-Reply-To: <20100430.164115.257514715.davem@davemloft.net>
On Fri, 30 Apr 2010, David Miller wrote:
> From: Tom Herbert <therbert@google•com>
> Date: Fri, 30 Apr 2010 00:58:32 -0700
>
> >> All these new checks and branches for a feature of questionable value.
> >
> >> If you can modify you apps to grab this information you can also probe
> >> for the information using external probing tools.
> >>
> > I don't see an nice way to do that, we're profiling a significant
> > percentage of millions of connections over thousands of paths as part
> > of standard operations while incurring negligible overhead. The app
> > can can easily timestamp its operations, but without some mechanism
> > for getting timestamps out of a TCP connection, the networking portion
> > of servicing requests is pretty much a black box in that.
>
> If other people have an opinion about this, now would be the time
> to speak up. :-)
Not being a kernel hacker, I will naively ask if the kernel tracing
facility could somehow be used to provide the desired info (or could
be modified to provide it).
-Bill
next prev parent reply other threads:[~2010-05-01 5:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 6:07 [PATCH] tcp: SO_TIMESTAMP implementation for TCP Tom Herbert
2010-04-30 6:39 ` David Miller
2010-04-30 7:58 ` Tom Herbert
2010-04-30 23:41 ` David Miller
2010-05-01 5:07 ` Bill Fink [this message]
2010-05-01 5:40 ` Tom Herbert
2010-05-01 6:00 ` Eric Dumazet
2010-05-01 5:31 ` Tom Herbert
2010-05-01 12:06 ` Paul LeoNerd Evans
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=20100501010735.dfe097bc.billfink@mindspring.com \
--to=billfink@mindspring$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=therbert@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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