mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Andrew Morton'" <akpm@osdl.org>
Cc: <nickpiggin@yahoo.com.au>, <mingo@elte.hu>,
	<linux-kernel@vger.kernel.org>
Subject: RE: [patch 0/2] fix perf. bug in wake-up load balancing for aim7 and db workload
Date: Mon, 13 Feb 2006 21:47:22 -0800	[thread overview]
Message-ID: <200602140547.k1E5lNg19060@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060213193856.696bf1f0.akpm@osdl.org>

Andrew Morton wrote on Monday, February 13, 2006 7:39 PM
> Post-mortem time.   Why was it merged?
> 
> This patch was added to -mm on 8 November 2006.  Was merged into mainline
> 12 January 2006.  That's two months in -mm and one month in mainline.
> 
> I don't think it's reasonable to stretch the latency of scheduler patches
> to even longer than three months and I doubt if that'll solve the problem.
> 
> Oh well, at least we found it.

I guess I'm the one to blame :-(  Our kernel performance project needs to
be more active in testing pending performance patches that sits in -mm.


> > We should back out the above commit and add a sysctl variable to control the
> > behavior of load balancing in wake up path, so user can dynamically select
> > a mode that best fit for the workload environment.  And kernel can achieve
> > best performance in two extreme ends of incompatible workload environments.
> 
> Well I don't see any benchmark numbers in the original patch.  Just an
> assertion that it "should" help something.
> 
> I'm more inclined to revert it and not add the sysctl (ugh) until we have a
> good reason to do so.

The discussion on wake-up load balancing started July 28 last year [1].
In that post, it was outlined that the performance patch gave 2.3% gain
for db transaction processing workload.  It was then followed up by a
couple of iterations, including one from Ingo[2] and one from Nick[3].

I think we just demonstrated that there are two workloads exist today
which has completely opposite requirement on load balancing in the
wake up path.  People has tried to make kernel smart and detect work-
load environment, but so far it hasn't worked.  And hence the sysctl
that I'm proposing right now.


[1] http://marc.theaimsgroup.com/?l=linux-kernel&m=112259224917701&w=2
[2] http://marc.theaimsgroup.com/?l=linux-kernel&m=112265450426975&w=2
[3] http://marc.theaimsgroup.com/?l=linux-kernel&m=113051195601837&w=2


  parent reply	other threads:[~2006-02-14  5:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2006-02-14  7:34   ` Ingo Molnar
2006-02-14  7:46 Chen, Kenneth W
2006-02-14  8:00 ` Andrew Morton
2006-02-14 12:47   ` Ingo Molnar
2006-02-14 18:31     ` Chen, Kenneth W
2006-02-14  8:04 Chen, Kenneth W

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=200602140547.k1E5lNg19060@unix-os.sc.intel.com \
    --to=kenneth.w.chen@intel.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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

all inboxes | Powered by JetHome®