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]
Date:	Wed, 19 Dec 2007 20:32:55 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Venki Pallipadi <venkatesh.pallipadi@...el.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, Len Brown <lenb@...nel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: Voluntary leave_mm before entering ACPI C3


* Venki Pallipadi <venkatesh.pallipadi@...el.com> wrote:

> Aviod TLB flush IPIs during C3 states by voluntary leave_mm() before 
> entering C3.
> 
> The performance impact of TLB flush on C3 should not be significant 
> with respect to C3 wakeup latency. Also, CPUs tend to flush TLB in 
> hardware while in C3 anyways.
> 
> On a 8 logical CPU system, running make -j2, the number of tlbflush 
> IPIs goes down from 40 per second to ~ 0. Total number of interrupts 
> during the run of this workload was ~1200 per second, which makes it 
> ~3% savings in wakeups.
> 
> There was no measurable performance or power impact however.

thanks, applied to x86.git. Nice and elegant patch!

Btw., since the TLB flush state machine is really subtle and fragile, 
could you try to run the following mmap stresstest i wrote some time 
ago:

   http://redhat.com/~mingo/threaded-mmap-stresstest/

for a couple of hours. It runs nr_cpus threads which then do a "random 
crazy mix" of mappings/unmappings/remappings of a 800 MB memory window. 
The more sockets/cores, the crazier the TLB races get ;-)

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ