netdev - [RFC]: add tracepoint to net_rx_action to note polling operations

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-next>] [day] [month] [year] [list]

Message-Id: <20090420211729.2218e5e2.nanog@85d5b20a518b8f6864949bd940457dc124746ddc.nosense.org>
Date:	Mon, 20 Apr 2009 21:17:29 +0930
From:	Mark Smith 
	<nanog@...5b20a518b8f6864949bd940457dc124746ddc.nosense.org>
To:	Neil Horman <nhorman@...driver.com>
Cc:	netdev@...r.kernel.org
Subject: [RFC]: add tracepoint to net_rx_action to note polling operations

Hi,

(not on list, please CC me)

"I was thinking about adding an additional tracepoint to
net_rx_action, right before the call to dev->poll().  One of the things
thats missing from my dropwatch utility is the ability to detect
hardware drops, and I was thinking I could implement that by noting
when devices were being polled by napi, and at that time querying the
devices stats.

	I know however, that adding tracepoints isn't always
desireable, so I thought I would solicit opinions here to see if anyone
else would find such a tracepoint usefull, or in the event they had
strong objectsions to such a point."

Would that be indicating that the host isn't keeping up with the
incoming packet rate? If so, I'd think that would be quite useful, as
it'd be a very obvious indicator that the host needs a performance
upgrade, should the traffic be valid e.g. not a DoS attack.

Regards,
Mark.

--
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