public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jonathan Zimmerman" <tyrius@nwlink.com>
To: linux-kernel@vger.kernel.org
Subject: softirq & schedule documentation
Date: Wed, 29 Aug 2001 09:29:55 -0700	[thread overview]
Message-ID: <3b8d1887.44fb.0@nwlink.com> (raw)

Hi,
  I'm in the process of trying to track down a problem with the sparc32 port

not booting and believe that the problem lies somewhere in either the scheduling

algorithm or ksoftirqd. Schedule is called by spawn_ksoftirqd, which then proceeds

to loop infinately. I know that, eventually, prev = current = next = ksoftirqd.

current->need_resched gets set to 0 in the move_rr_back block of schedule(),

but at some point in recalculate: it gets set back to 1.

Is there any sort of documentation on the softirq stuff and the scheduling algorithm

out there that is relevant to 2.4.9? It seems that the only stuff I've managed

to find is based off the 2.2.x kernels.

Thanks,

Jonathan Zimmerman

             reply	other threads:[~2001-08-29 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-29 16:29 Jonathan Zimmerman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-30 14:27 softirq & schedule documentation Shailabh Nagar

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=3b8d1887.44fb.0@nwlink.com \
    --to=tyrius@nwlink.com \
    --cc=linux-kernel@vger.kernel.org \
    /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