netdev - RE: [PATCH v2 0/2] Tracepoint for tcp retransmission

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <65795E11DBF1E645A09CEC7EAEE94B9CB8E7B0F3@USINDEVS02.corp.hds.com>
Date:	Mon, 6 Feb 2012 13:32:33 -0500
From:	Satoru Moriya <satoru.moriya@....com>
To:	Yuchung Cheng <ycheng@...gle.com>
CC:	David Miller <davem@...emloft.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"nhorman@...driver.com" <nhorman@...driver.com>,
	"tgraf@...radead.org" <tgraf@...radead.org>,
	"stephen.hemminger@...tta.com" <stephen.hemminger@...tta.com>,
	"hagen@...u.net" <hagen@...u.net>,
	"eric.dumazet@...il.com" <eric.dumazet@...il.com>,
	Seiji Aguchi <seiji.aguchi@....com>
Subject: RE: [PATCH v2 0/2] Tracepoint for tcp retransmission

On 02/03/2012 11:40 PM, Yuchung Cheng wrote:
> I totally understand that you need deeper instrumentation for *your* 
> business. At Google, we instrument a lot more in TCP as well. But we 
> have yet to upstream these changes because it's not universally useful 
> for default Linux kernel. I failed to see how different failures of a 
> TCP retransmission must be recorded and exported. Could you elaborate 
> your last point?

Hi Yuchung,

Ultimately, we'd like to record all the tcp retransmission failures
but for the first step, we'd like to know whether kernel succeeded
retransmission or not (kernel sent a packet or not).

Does it make sense?

Regards,
Satoru
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html