From: Ingo Molnar <mingo@elte.hu>
To: Venki Pallipadi <venkatesh.pallipadi@intel.com>
Cc: 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: Thu, 20 Dec 2007 10:31:39 +0100 [thread overview]
Message-ID: <20071220093138.GE4478@elte.hu> (raw)
In-Reply-To: <20071220020846.GA13464@linux-os.sc.intel.com>
* Venki Pallipadi <venkatesh.pallipadi@intel.com> wrote:
> > 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.
ok, great. Regarding power consumption: i suspect a real difference will
only show up on multi-socket systems that can do deeper C modes, or on
multicore systems that will benefit from longer idle time on another
core. (i suspect most multicore CPUs today will only truly save
significant amounts of power if all cores are idle.) In any case, not
doing these extra IPIs is definitely a plus.
Ingo
prev parent reply other threads:[~2007-12-20 9:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 18:34 [PATCH] x86: Voluntary leave_mm before entering ACPI C3 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
2007-12-20 9:31 ` Ingo Molnar [this message]
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=20071220093138.GE4478@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.