From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
nickpiggin@yahoo.com.au, linux-kernel@vger.kernel.org
Subject: Re: [patch 0/2] fix perf. bug in wake-up load balancing for aim7 and db workload
Date: Tue, 14 Feb 2006 13:47:43 +0100 [thread overview]
Message-ID: <20060214124743.GA5586@elte.hu> (raw)
In-Reply-To: <20060214000033.7e695978.akpm@osdl.org>
* Andrew Morton <akpm@osdl.org> wrote:
> "Chen, Kenneth W" <kenneth.w.chen@intel.com> wrote:
> >
> > Here is a respin of the patch with more documentation.
> >
>
> Thanks. Can you send me an unwordwrapped version off-list?
>
> Did I mention "ug"?
>
> Ingo, what's your plan here?
I really dont like the sysctl hack. Firstly, which precise kernel
version was tested - do we know that it wasnt e.g. the smpnice
regression interfering? Secondly, i dont like the sysctl concept itself:
i really think we should try to find a way for _applications_ to be
woken up according to their workload.
If we add the sysctl then basically only the benchmarkers will use it -
99.99% of users will get whatever default we (and distros) provide, and
the problem wont be solved in any way. In fact, we'll never be able to
get rid of the knob again i suspect. I'd rather have the wakeup patch
reverted, and some better method presented. Adding the sysctl just
removes all the incentive for people to work on solving this problem in
some real way.
I also refuse to regard this as any sort of emergency that justifies the
sysctl hack. The test results came clearly late and i suggested to the
benchmarking guys a long time ago that if they want us to care about
their workload, and if it's complex to reproduce the benchmark, they
should distill some simpler test-app for us to so that we can reproduce
those cases. I'd much rather like to do the simplest thing: revert the
wakeup patch (we were fine without it for 15 kernel releases), than to
paper over [permanently!] this particular incarnation of a wider
problem.
Ingo
next prev parent reply other threads:[~2006-02-14 12:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 7:46 [patch 0/2] fix perf. bug in wake-up load balancing for aim7 and db workload Chen, Kenneth W
2006-02-14 8:00 ` Andrew Morton
2006-02-14 12:47 ` Ingo Molnar [this message]
2006-02-14 18:31 ` Chen, Kenneth W
-- strict thread matches above, loose matches on Subject: below --
2006-02-14 8:04 Chen, Kenneth W
2006-02-14 3:09 Chen, Kenneth W
2006-02-14 3:38 ` Andrew Morton
2006-02-14 3:44 ` Nick Piggin
2006-02-14 3:57 ` Nick Piggin
2006-02-14 4:13 ` Andrew Morton
2006-02-14 3:59 ` Andrew Morton
2006-02-14 6:13 ` Chen, Kenneth W
2006-02-14 5:47 ` Chen, Kenneth W
2006-02-14 7:34 ` 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=20060214124743.GA5586@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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