public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gaurav Dhiman <gaurav4lkg@gmail.com>
To: "Sat." <walking.to.remember@gmail.com>
Cc: Christopher Friesen <cfriesen@nortel.com>, linux-kernel@vger.kernel.org
Subject: Re: when or where can the case occur in "linux kernel development " about "kernel preemption"?
Date: Sun, 28 Aug 2005 12:35:42 +0530	[thread overview]
Message-ID: <1e33f571050828000537648e5b@mail.gmail.com> (raw)
In-Reply-To: <6b5347dc050827085727df49c8@mail.gmail.com>

On 8/27/05, Sat. <walking.to.remember@gmail.com> wrote:
> 2005/8/27, Christopher Friesen <cfriesen@nortel.com>:
> > Sat. wrote:
> > > the case about kernel preemption as follow :
> > >
> > > the book said "when a process that has a higher priority than the
> > > currenty running process is awakened ".
> > >
> > > but I can think about when such case can occur , could you give me an example ?
> >
> > There may be others, but one common case is when a hardware interrupt
> > causes the higher priority process to become runnable.  Some examples of
> > this would be a network packet arriving, or the expiry of a hardware timer.
> >
> > Chris
> >
> 
> unfortunately, I cannot agree with you , normally ,when the kernel
> runs in interrupt context , the schedule() should not be invoked
> ------my views .
> 

Its not actually the interrupt handler which calls the schedule()
function, rather interrupt handler just perform the minimal task, like
copying the data from network card buffer to kernel buffer in case of
packet arriving on system. Its the other function which actually
interrut handler schedules for later invocation and this later
invocation is done in process context and so the function scheduled
for later invocation can wake the waiting processes and can call
schedule() function if needed.

I hope I am not wrong ;-)
-Gaurav

> then,could anyone  give me a definite example about network like above
> or anything else to eluminate  this , ok?
> 
> thanks !
> 
> --
> Sat.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

  reply	other threads:[~2005-08-28  7:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-26 16:20 when or where can the case occur in "linux kernel development " about "kernel preemption"? Sat.
2005-08-26 16:40 ` Christopher Friesen
2005-08-27 15:57   ` Sat.
2005-08-28  7:05     ` Gaurav Dhiman [this message]
2005-08-29 11:46     ` linux-os (Dick Johnson)
2005-08-29 17:54       ` George Anzinger

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=1e33f571050828000537648e5b@mail.gmail.com \
    --to=gaurav4lkg@gmail.com \
    --cc=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=walking.to.remember@gmail.com \
    /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