From: Mike Galbraith <efault@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Valdis.Kletnieks@vt.edu, Mike Travis <travis@sgi.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
mm-commits@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>,
Dave Jones <davej@redhat.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: mmotm 2009-04-10-02-21 uploaded - forkbombed by work_for_cpu
Date: Mon, 13 Apr 2009 18:34:48 +0200 [thread overview]
Message-ID: <1239640488.7866.4.camel@marge.simson.net> (raw)
In-Reply-To: <alpine.LFD.2.00.0904130847500.4583@localhost.localdomain>
On Mon, 2009-04-13 at 09:04 -0700, Linus Torvalds wrote:
> So afaik, acpi-cpufreq.c should not use "work_on_cpu()" for that at all.
> It should just do a smp_call_function_single().
Andrew already fixed it to use smp_call_function_single() because of
another regression. (mysql+oltp took 10% peak throughput hit here)
-Mike
next prev parent reply other threads:[~2009-04-13 16:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 9:22 mmotm 2009-04-10-02-21 uploaded akpm
2009-04-10 19:53 ` mmotm 2009-04-10-02-21 uploaded (shmem) Randy Dunlap
2009-04-10 20:00 ` Andrew Morton
2009-04-10 20:04 ` Randy Dunlap
2009-04-10 20:16 ` Hugh Dickins
2009-04-11 13:22 ` mmotm 2009-04-10-02-21 uploaded - forkbombed by work_for_cpu Valdis.Kletnieks
2009-04-13 16:04 ` Linus Torvalds
2009-04-13 16:34 ` Mike Galbraith [this message]
2009-04-13 17:18 ` Ingo Molnar
2009-04-13 17:27 ` Andrew Morton
2009-04-13 17:27 ` Andrew Morton
2009-04-13 17:41 ` Ingo Molnar
2009-04-13 17:45 ` Linus Torvalds
2009-04-13 18:11 ` Ingo Molnar
2009-04-13 18:49 ` Andrew Morton
2009-04-13 19:03 ` Jeremy Fitzhardinge
2009-04-13 19:03 ` Dave Jones
2009-04-13 19:40 ` Ingo Molnar
2009-04-13 19:27 ` Valdis.Kletnieks
2009-04-13 23:50 ` Linus Torvalds
2009-04-14 0:31 ` Andrew Morton
2009-04-15 8:15 ` Ali Gholami Rudi
2009-04-15 8:34 ` Andrew Morton
2009-04-15 8:34 ` Andrew Morton
2009-04-15 9:08 ` Ali Gholami Rudi
2009-04-15 14:45 ` Linus Torvalds
2009-04-14 12:42 ` Rusty Russell
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=1239640488.7866.4.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.org \
--cc=travis@sgi.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.