From: Anders Fugmann <afu@fugmann.dhs.org>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Q: Scheduler and need_resched
Date: Tue, 24 Sep 2002 11:37:38 +0200 [thread overview]
Message-ID: <3D903262.3020003@fugmann.dhs.org> (raw)
In-Reply-To: 3D9026B6.3080509@fugmann.dhs.org
Anders Fugmann wrote:
> Hi.
>
> I got a small question of what happens codevice when the quantum of a
> task is expired (counter == 0 -> need_resched == 1). Of cource schedule
> is invoked somehow, but from where? How is the "flow". I see from where
> do_timer is called, and that it schedules a BH, but then I'm stuck.
>
> Any pointer appriciated.
> Anders Fugmann
Solved.
By the help of the kernel newbies pages, I was pointed to the page
http://kernelnewbies.org/wiki/moin.cgi/Karthick, which pointed at
the label '_ret_with_reschedule' in entry.S.
This piece of assembler is called after each interrupt, and tests the
need_resched flag to see is scheduling is nessesary.
Anyway, thanks for your time.
Anders Fugmann
prev parent reply other threads:[~2002-09-24 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 8:47 Q: Scheduler and need_resched Anders Fugmann
2002-09-24 9:37 ` Anders Fugmann [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=3D903262.3020003@fugmann.dhs.org \
--to=afu@fugmann.dhs.org \
--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