public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Herman Oosthuysen <herman@wirelessnetworksinc.com>
To: "linux-mtd@lists.infrared.org" <linux-mtd@lists.infradead.org>
Subject: Re: Why timer interrupt is disabled?
Date: Fri, 25 May 2001 11:06:11 -0600	[thread overview]
Message-ID: <01052511093801.00873@localhost.localdomain> (raw)
In-Reply-To: <1765.990808662@redhat.com>

On Fri, 25 May 2001, David Woodhouse wrote:
> The kernel is not preemptively scheduled. Unless the first process 
> explicitly calls schedule(), it's not going to lose the CPU. Only processes 
> in user mode are scheduled from the timer IRQ.

Is it not dangerous to assume that the kernel is non-preemptive?
MTD is after all most likely to be used in a real-time system, which may very
well have a different scheduler from the common/garden variety Linux.

Cheers,
-- 
Herman Oosthuysen
Phone: 403+569-5687
E-mail: Herman@WirelessNetworksInc.com

  reply	other threads:[~2001-05-25 17:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-25 13:04 Why timer interrupt is disabled? andreev
2001-05-25 13:12 ` David Woodhouse
     [not found]   ` <3B0EE338.1000701@niisi.msk.ru>
2001-05-25 15:17     ` David Woodhouse
2001-05-26  0:17       ` Alexandr Andreev
2001-05-25 16:37         ` David Woodhouse
2001-05-25 17:06           ` Herman Oosthuysen [this message]
2001-05-26  1:31           ` Alexandr Andreev
2001-05-25 17:36             ` David Woodhouse
     [not found] <3B0EE8CF.7040502@niisi.msk.ru>
     [not found] ` <20010526000119.A23273@suse.de>
2001-05-28 19:07   ` Alexandr Andreev
2001-05-28 15:36     ` David Woodhouse

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=01052511093801.00873@localhost.localdomain \
    --to=herman@wirelessnetworksinc.com \
    --cc=linux-mtd@lists.infradead.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