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 for Android: free password hash cracker in your pocket

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

Message-Id: <20120205.164812.383526470219039003.davem@davemloft.net>
Date:	Sun, 05 Feb 2012 16:48:12 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	hagen@...u.net
Cc:	nhorman@...driver.com, fche@...stic.org, satoru.moriya@....com,
	netdev@...r.kernel.org, tgraf@...radead.org,
	stephen.hemminger@...tta.com, eric.dumazet@...il.com,
	seiji.aguchi@....com, fche@...rceware.org,
	mathieu.desnoyers@...ymtl.ca, rostedt@...dmis.org
Subject: Re: [PATCH v2 0/2] Tracepoint for tcp retransmission

Let me put an end to this dicussion right now, I'm not applying
any patches which just add tracepoints into the TCP stack.

That's not the solution, and you can hoot and hollar all you want
about it, I simply do not care.

The solution is a way to manage socket events, and be able to choose
which sockets emit those events, in a useful way, via the perf event
infrastructure.

This means we need a perf event socket layer that allows filtering on
socket flow ID, which enables per-socket event and statistics
gathering, and so forth.
--
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