public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Anton Blanchard <anton@samba.org>,
	mingo@elte.hu, linux-kernel@vger.kernel.org, msb@google.com
Subject: Re: PATCH: softlockup: Fix hung_task_check_count sysctl
Date: Fri, 27 Nov 2009 03:55:13 +0100	[thread overview]
Message-ID: <20091127025512.GB5406@nowhere> (raw)
In-Reply-To: <2375c9f90911261846i18a828eft391420b13bb3fbb2@mail.gmail.com>

On Fri, Nov 27, 2009 at 10:46:53AM +0800, Américo Wang wrote:
> On Fri, Nov 27, 2009 at 10:28 AM, Anton Blanchard <anton@samba.org> wrote:
> >
> > I'm seeing spikes of up to 0.5ms in khungtaskd on a large machine. To reduce
> > this source of jitter I tried setting hung_task_check_count to 0:
> >
> > # echo 0 > /proc/sys/kernel/hung_task_check_count
> >
> > which didn't have the intended response. Change to a post increment of
> > max_count, so a value of 0 means check 0 tasks.
> >
> > Signed-off-by: Anton Blanchard <anton@samba.org>
> 
> 
> Ack.
> 
> I would also suggest to make 'max_count' as unsigned long,
> since sysctl_hung_task_check_count is.
> 
> Thanks.


Also, the batch_count thing should be dropped I think.
This is a hardcoded, not overridable pause after 1024
threads checks to avoid latencies caused by rcu_read_lock.
But now we have PREEMPT_RCU so people can enable it if
they care about latency. We should remove it as it adds
unnecessary complexity.

I'm preparing a patch for that, on top of Anton patch.


  reply	other threads:[~2009-11-27  2:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-27  2:28 PATCH: softlockup: Fix hung_task_check_count sysctl Anton Blanchard
2009-11-27  2:40 ` Frederic Weisbecker
2009-11-27  2:46 ` Américo Wang
2009-11-27  2:55   ` Frederic Weisbecker [this message]
2009-11-27  3:02     ` Américo Wang
2009-11-27  4:22       ` Frederic Weisbecker
2009-11-27  5:48 ` [tip:core/softlockup] " tip-bot for Anton Blanchard
2009-11-30 19:13 ` PATCH: " Mandeep Singh Baines
2009-11-30 20:21   ` Mandeep Baines

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=20091127025512.GB5406@nowhere \
    --to=fweisbec@gmail.com \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=msb@google.com \
    --cc=xiyou.wangcong@gmail.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