From: Russell King <rmk@arm.linux.org.uk>
To: Francis Litterio <franl@world.std.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does the scheduler run every time jiffies is incremented?
Date: Sun, 22 Apr 2001 16:04:55 +0100 [thread overview]
Message-ID: <20010422160455.F20807@flint.arm.linux.org.uk> (raw)
In-Reply-To: <m31yql2di8.fsf@chantale.std.com>
In-Reply-To: <m31yql2di8.fsf@chantale.std.com>; from franl@world.std.com on Sun, Apr 22, 2001 at 10:52:15AM -0400
On Sun, Apr 22, 2001 at 10:52:15AM -0400, Francis Litterio wrote:
> Does the scheduler run every time jiffies is incremented?
No, it runs when something needs to be rescheduled (ie, when
the current tasks need_resched element (current->need_resched) is set).
This typically happens when someone wakes up, or the task reaches the
end of its allotted quantum.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
prev parent reply other threads:[~2001-04-22 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-22 14:52 Does the scheduler run every time jiffies is incremented? Francis Litterio
2001-04-22 14:59 ` Rik van Riel
2001-04-22 15:04 ` Russell King [this message]
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=20010422160455.F20807@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=franl@world.std.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