The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: RE: How does the kernel interrupt a user process with code while (1) {}?
Date: Wed, 1 Nov 2006 13:03:32 -0800	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKAEHEPHAB.davids@webmaster.com> (raw)
In-Reply-To: <3dd9a95e0611010712j9f4c021m1673eeda6af30c49@mail.gmail.com>


> Thanks.
>
> On 11/1/06, Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
> > >
> > > As title, thanks ;-)
> >
> > Timer interrupt.

Other interrupts too. For example, if a disk I/O operation completes (or a
network packet is received) and generates an interrupt, the kernel could use
that interrupt to switch to another process made ready-to-run by the disk
operation or data received over the network.

Any interrupt can interrupt a user process.

DS



  reply	other threads:[~2006-11-01 21:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01  9:59 How does the kernel interrupt a user process with code while (1) {}? Xiao Niu
2006-11-01 11:02 ` Jan Engelhardt
2006-11-01 15:12   ` Xiao Niu
2006-11-01 21:03     ` David Schwartz [this message]
     [not found] ` <df9815e70611010215i69a8fbe5id381bdaa357388ae@mail.gmail.com>
2006-11-01 15:12   ` Xiao Niu

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=MDEHLPKNGKAHNMBLJOLKAEHEPHAB.davids@webmaster.com \
    --to=davids@webmaster.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