From: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
To: Dhaval Giani <dhaval@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Balbir Singh <balbir@in.ibm.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: System hangs on running kernbench
Date: Tue, 24 Jul 2007 12:43:20 +0530 [thread overview]
Message-ID: <20070724071320.GA12169@linux.vnet.ibm.com> (raw)
In-Reply-To: <20070718075648.GA4235@linux.vnet.ibm.com>
On Wed, Jul 18, 2007 at 01:26:48PM +0530, Dhaval Giani wrote:
> Hi Andrew,
>
> I was running kernbench on top of 2.6.22-rc6-mm1 and I got a Hangcheck
> alert (This is when kernbench reached make -j).
>
> Also make -j is hanging.
[refer http://marc.info/?l=linux-kernel&m=118474574807055 for complete
report of this bug]
Ingo,
Dhaval tracked the root cause of this problem to be in cfs (btw
cfs patches weren't git-bisect safe).
Basically, "make -s -j" workload hanged the machine, leading to lot of
OOM killings. This was on a 8-cpu machine with no swap space configured and
4GB RAM. The same workload works "fine" (runs to completion) on 2.6.22.
I played with the scheduler tunables a bit and found that the problem
goes away if I set sched_granularity_ns to 100ms (default value 32ms).
So my theory is this: 32ms preemption granularity is too low value for
any compile thread to make "usefull" progress. As a result of this rapid
context switch, job retiral rate slows down compared to job arrival
rate. This builds up job pressure on the system very quickly (than may
have happened with 100ms default granularity_ns or 2.6.22 kernel),
leading to OOM killings (and hang).
>From a user perspective, who is running with default granularity_ns
value, this may be seen as a regression.
Perhaps, these new tunables in cfs are something for users to become used to
and tune it to approp setting for their system. It would have been
nice for kernel to auto-tune the settings based on workload, but I guess
that's harder.
--
Regards,
vatsa
next prev parent reply other threads:[~2007-07-24 7:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 7:56 System hangs on running kernbench Dhaval Giani
2007-07-18 8:07 ` Andrew Morton
2007-07-18 9:41 ` Dhaval Giani
2007-07-18 14:46 ` Dhaval Giani
2007-07-19 6:28 ` Dhaval Giani
2007-07-19 6:34 ` Dhaval Giani
2007-07-18 15:08 ` Chuck Ebbert
2007-07-19 4:47 ` Dhaval Giani
2007-07-24 7:13 ` Srivatsa Vaddagiri [this message]
2007-07-24 8:19 ` 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=20070724071320.GA12169@linux.vnet.ibm.com \
--to=vatsa@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@in.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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