From: Venki Pallipadi <venkatesh.pallipadi@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Venki Pallipadi <venkatesh.pallipadi@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Len Brown <lenb@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Voluntary leave_mm before entering ACPI C3
Date: Wed, 19 Dec 2007 18:08:47 -0800 [thread overview]
Message-ID: <20071220020846.GA13464@linux-os.sc.intel.com> (raw)
In-Reply-To: <20071219193255.GA2158@elte.hu>
On Wed, Dec 19, 2007 at 08:32:55PM +0100, Ingo Molnar wrote:
>
> * Venki Pallipadi <venkatesh.pallipadi@intel.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,
I ran this stress test on two systems (8 cores and 2 cores) for over
4 hours without any issues. There was more than 20% C3 time during the
run. So, this C3 tlbflush path must have been stressed well during the run.
And sorry about the patch not working on UP config. That was a silly oversight
on my part.
Thanks,
Venki
next prev parent reply other threads:[~2007-12-20 2:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 18:34 Venki Pallipadi
2007-12-19 19:32 ` Ingo Molnar
2007-12-19 19:36 ` H. Peter Anvin
2007-12-19 19:40 ` Ingo Molnar
2007-12-19 19:48 ` H. Peter Anvin
2007-12-19 20:23 ` Venki Pallipadi
2007-12-20 7:53 ` Arjan van de Ven
2007-12-20 16:16 ` H. Peter Anvin
2007-12-20 18:22 ` Arjan van de Ven
2007-12-20 18:32 ` H. Peter Anvin
2007-12-20 19:28 ` Len Brown
2007-12-19 19:56 ` Venki Pallipadi
2007-12-19 20:54 ` Ingo Molnar
2007-12-20 2:08 ` Venki Pallipadi [this message]
2007-12-20 9:31 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071220020846.GA13464@linux-os.sc.intel.com \
--to=venkatesh.pallipadi@intel.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®