From: "Stephen C. Tweedie" <sct@redhat.com>
To: pnilesh@in.ibm.com
Cc: linux-mm@kvack.org
Subject: Re: preemp / nonpreemp
Date: Tue, 18 Apr 2000 10:18:01 +0100 [thread overview]
Message-ID: <20000418101801.I3916@redhat.com> (raw)
In-Reply-To: <CA2568C5.0017E931.00@d73mta05.au.ibm.com>; from pnilesh@in.ibm.com on Tue, Apr 18, 2000 at 09:42:27AM +0530
Hi,
On Tue, Apr 18, 2000 at 09:42:27AM +0530, pnilesh@in.ibm.com wrote:
> The Linux kernel is preemptable.
Not by any normal definition. The kernel is not preempted: any
scheduler interrupt which occurs while kernel code is running will
not cause a reschedule.
Kernel code _can_ be rescheduled, but only explicitly by calling
schedule(), or implicitly by calling some function which performs
a sleeping operation (including page faults).
>
> Does the preemption mean that inside system calls in kernel a call to
> schedule is possible .
It is possible, yes, but it will not happen in a preemptive manner.
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-04-18 9:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-18 4:12 preemp / nonpreemp pnilesh
2000-04-18 6:40 ` Eric W. Biederman
2000-04-18 9:18 ` Stephen C. Tweedie [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-18 8:20 pnilesh
2000-04-18 9:22 ` Stephen C. Tweedie
2000-04-18 10:49 pnilesh
2000-04-18 11:23 ` Stephen C. Tweedie
[not found] <CA2568C5.002E8BFC.00@d73mta03.au.ibm.com>
2000-04-18 15:03 ` Eric W. Biederman
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=20000418101801.I3916@redhat.com \
--to=sct@redhat.com \
--cc=linux-mm@kvack.org \
--cc=pnilesh@in.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.