mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Mikael Starvik <mikael.starvik@axis.com>
Cc: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: Re: Very long startup time for a new thread
Date: Thu, 13 Jul 2006 09:36:03 +0200	[thread overview]
Message-ID: <1152776163.8627.38.camel@Homer.TheSimpsons.net> (raw)
In-Reply-To: <BFECAF9E178F144FAEF2BF4CE739C668030B55B0@exmail1.se.axis.com>

On Thu, 2006-07-13 at 08:07 +0200, Mikael Starvik wrote:
> (This is on a 200 MIPS embedded architecture).
> 
> On a heavily loaded system (loadavg ~4) I create a new pthread. In this
> situation it takes ~4 seconds (!) before the thread is first scheduled in
> (yes, I have debug outputs in the scheduler to check that). In a 2.4 based
> system I don't see the same thing. I don't have any RT or FIFO tasks. Any
> ideas why it takes so long time and what I can do about it?

If your new thread is runnable but not selected for those ~4 seconds, it
could be the interactivity code.  Try disabling that.

If you want to try a patch that targets this area, I have an old one for
2.6.16 you can play with.  With it, you can pretty much disable the
interactivity code without losing dynamic priority adjustment.  I also
have one for 2.6.17, and that one removes the interactivity code
entirely (hmm) but it also actively intervenes in scheduling decisions,
so might not be a good diagnostic.

	-Mike


  parent reply	other threads:[~2006-07-13  7:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13  6:07 Mikael Starvik
2006-07-13  7:14 ` Arjan van de Ven
2006-07-13  7:36 ` Mike Galbraith [this message]
     [not found] <BFECAF9E178F144FAEF2BF4CE739C66803F33440@exmail1.se.axis.com>
2006-07-13  7:51 ` Mikael Starvik
2006-07-17  8:44 Mikael Starvik

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=1152776163.8627.38.camel@Homer.TheSimpsons.net \
    --to=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikael.starvik@axis.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®