From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Chris Mason'" <mason@suse.com>,
"Con Kolivas" <kernel@kolivas.org>,
<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH RFC] smt nice introduces significant lock contention
Date: Thu, 1 Jun 2006 16:57:15 -0700 [thread overview]
Message-ID: <000101c685d7$1bc84390$d234030a@amr.corp.intel.com> (raw)
In-Reply-To: <200606011855.38110.mason@suse.com>
Chris Mason wrote on Thursday, June 01, 2006 3:56 PM
> Hello everyone,
>
> Recent benchmarks showed some performance regressions between 2.6.16 and
> 2.6.5. We tracked down one of the regressions to lock contention in schedule
> heavy workloads (~70,000 context switches per second)
>
> kernel/sched.c:dependent_sleeper() was responsible for most of the lock
> contention, hammering on the run queue locks. The patch below is more of
> a discussion point than a suggested fix (although it does reduce lock
> contention significantly). The dependent_sleeper code looks very expensive
> to me, especially for using a spinlock to bounce control between two different
> siblings in the same cpu.
Yeah, this also sort of echo a recent discovery on one of our benchmarks
that schedule() is red hot in the kernel. I was just scratching my head
not sure what's going on. This dependent_sleeper could be the culprit
considering it is called almost at every context switch. I don't think
we are hitting on lock contention, but by the large amount of code it
executes. It really needs to be cut down ....
- Ken
next prev parent reply other threads:[~2006-06-01 23:57 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 22:55 Chris Mason
2006-06-01 23:57 ` Chen, Kenneth W [this message]
2006-06-02 1:59 ` Con Kolivas
2006-06-02 2:28 ` Con Kolivas
2006-06-02 3:55 ` Con Kolivas
2006-06-02 4:18 ` Nick Piggin
2006-06-02 6:08 ` Con Kolivas
2006-06-02 7:53 ` Nick Piggin
2006-06-02 8:17 ` Con Kolivas
2006-06-02 8:28 ` Nick Piggin
2006-06-02 8:34 ` Chen, Kenneth W
2006-06-02 8:56 ` Nick Piggin
2006-06-02 9:17 ` Chen, Kenneth W
2006-06-02 9:25 ` Con Kolivas
2006-06-02 9:31 ` Chen, Kenneth W
2006-06-02 9:34 ` Con Kolivas
2006-06-02 9:53 ` Chen, Kenneth W
2006-06-02 10:12 ` Con Kolivas
2006-06-02 20:53 ` Chen, Kenneth W
2006-06-02 22:15 ` Con Kolivas
2006-06-02 22:19 ` Chen, Kenneth W
2006-06-02 22:31 ` Con Kolivas
2006-06-02 22:58 ` Chen, Kenneth W
2006-06-03 0:02 ` Con Kolivas
2006-06-03 0:08 ` Chen, Kenneth W
2006-06-03 0:27 ` Con Kolivas
2006-06-02 9:36 ` Chen, Kenneth W
2006-06-02 10:30 ` Con Kolivas
2006-06-02 13:16 ` Con Kolivas
2006-06-02 21:54 ` Chen, Kenneth W
2006-06-02 22:04 ` Con Kolivas
2006-06-02 22:14 ` Chen, Kenneth W
2006-06-02 10:19 ` Con Kolivas
2006-06-02 20:59 ` Chen, Kenneth W
2006-06-02 8:38 ` Chen, Kenneth W
2006-06-02 8:24 ` Chen, Kenneth W
2006-06-02 8:31 ` Chen, Kenneth W
2006-06-02 8:50 ` Chen, Kenneth W
2006-06-02 2:35 ` Chen, Kenneth W
2006-06-02 3:04 ` Con Kolivas
2006-06-02 3:23 ` Con Kolivas
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='000101c685d7$1bc84390$d234030a@amr.corp.intel.com' \
--to=kenneth.w.chen@intel.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome