linux-kernel - Re: [patch 0/7] timers: Footprint diet and NOHZ overhead mitigation

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

Message-ID: <alpine.DEB.2.11.1506021449200.3786@nanos>
Date:	Tue, 2 Jun 2015 15:58:33 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Eric Dumazet <eric.dumazet@...il.com>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Paul McKenney <paulmck@...ux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Eric Dumazet <edumazet@...gle.com>,
	Viresh Kumar <viresh.kumar@...aro.org>,
	John Stultz <john.stultz@...aro.org>,
	Joonwoo Park <joonwoop@...eaurora.org>,
	Wenbo Wang <wenbo.wang@...blaze.com>
Subject: Re: [patch 0/7] timers: Footprint diet and NOHZ overhead
 mitigation

On Wed, 27 May 2015, Eric Dumazet wrote:
> I finally got back two hosts with 72 cpus where I can try your patches.

Waiting for your results :)

> I have one comment about socket TCP timers : They are re-armed very
> often, but they are never canceled (unless the socket is dismantled)
> 
> I am too lazy to search for the commit adding this stuff (before git),
> but I guess it helped a lot RPC sessions : No need to cancel a timer if
> we're likely to rearm it in the following 10 usec ;)

Right, but that's a 'cancel + rearm' in the timer core code, unless
the expiry time does not change.

Thanks,

	tglx

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/