[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <65795E11DBF1E645A09CEC7EAEE94B9CB8D3EA3E@USINDEVS02.corp.hds.com>
Date: Fri, 3 Feb 2012 15:43:30 -0500
From: Satoru Moriya <satoru.moriya@....com>
To: Hagen Paul Pfeifer <hagen@...u.net>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"nhorman@...driver.com" <nhorman@...driver.com>,
"tgraf@...radead.org" <tgraf@...radead.org>,
Stephen Hemminger <stephen.hemminger@...tta.com>,
"eric.dumazet@...il.com" <eric.dumazet@...il.com>,
Seiji Aguchi <seiji.aguchi@....com>
Subject: RE: [PATCH v2 0/2] Tracepoint for tcp retransmission
On 01/25/2012 08:27 AM, Hagen Paul Pfeifer wrote:
> It is crazy to add everywhere new tracepoints. Systemtap is far from
> being perfect and as smooth as dtrace. But this is an example where
> systemtap is suitable and should be used.
>
> Satoru, you wrote systemtap is not suitable - why?
Actually, we've already used systemtap in our flight recorder.
But we believe that tcp retransmission is one of the fundamental
function in tcp stack and so kernel itself should provide the
instruments from which we can get enough information without
tools which is not included in kernel.
Regards,
Satoru
Powered by blists - more mailing lists