mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Ray Jui <rjui@broadcom.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Questions about Linux workqueue in 2.6.36
Date: Wed, 16 Feb 2011 17:52:55 +0100	[thread overview]
Message-ID: <20110216165255.GJ19830@htj.dyndns.org> (raw)
In-Reply-To: <8628FE4E7912BF47A96AE7DD7BAC0AADDDF03CDD8A@SJEXCHCCR02.corp.ad.broadcom.com>

Hello,

On Tue, Feb 15, 2011 at 09:57:21AM -0800, Ray Jui wrote:
> Regarding your second patch, which changes the initial mayday timeout to
> MAYDAY_INITIAL_TIMEOUT	= HZ / 100 >= 2 ? HZ / 100 : 2,
> 
> That's a minimum of 2 timer ticks, which is 20 ms in our
> system. Since the timer resolution in our system is 10 ms and it
> takes 15 ~ 20 ms to create a new kworker during kernel startup in
> our system, I verified that I need to change the minimum timer tick
> to 3 for the rescuer NOT to kick in our system during startup.

I think calling rescuers in that case is not perfect but okay.  It'll
only happen while the level of workers is below stable level.  It
would still be better to avoid calling in rescuers almost immediately
with 0 or 1 jiffy timeout.

Thanks.

-- 
tejun

  reply	other threads:[~2011-02-16 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8628FE4E7912BF47A96AE7DD7BAC0AADDDF02C2EAC@SJEXCHCCR02.corp.ad.broadcom.com>
     [not found] ` <20110209102847.GE3770@htj.dyndns.org>
2011-02-09 22:38   ` Ray Jui
2011-02-14 13:03     ` Tejun Heo
2011-02-14 13:09       ` [PATCH wq#fixes-2.6.38] workqueue: wake up a worker when a rescuer is leaving a gcwq Tejun Heo
2011-02-15 17:57       ` Questions about Linux workqueue in 2.6.36 Ray Jui
2011-02-16 16:52         ` Tejun Heo [this message]
2011-02-16 17:19           ` [PATCH wq#fixes-2.6.38] workqueue: make sure MAYDAY_INITIAL_TIMEOUT is at least 2 jiffies long Tejun Heo

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=20110216165255.GJ19830@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjui@broadcom.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
all inboxes | Powered by JetHome®