From: Anders Peter Fugmann <afu@fugmann.dhs.org>
To: Samuel T Ting <sting@u.washington.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Preemptive kernel and vm management in 2.4.9
Date: Fri, 21 Sep 2001 10:48:12 +0200 [thread overview]
Message-ID: <3BAAFECC.9060701@fugmann.dhs.org> (raw)
In-Reply-To: <Pine.A41.4.33.0109201717570.102458-100000@dante09.u.washington.edu>
The preemption patch helps on problems with high letencies.
High latencies means that the kernel is busy doing something, so that
other threads will get starved. This problem is especially seen when
using multimedia.
The most discussed problem is listening to a MP3-file, while the machine
has a high load. What we want to avoid is skips in the music.
Tee preemption patch helps, because it allows preemption of processes
running in kernel space, meaning that the sheduler can choose another
process, even though the process running is in kernel-space.
(A very crude description, I know, but AFAIK is is the general idea)
Without the preemption patch, whenever a userprocess makes a call to the
kernel, it could not be resheduled before the call had returned. This
results in very high latencies for some kernel calls.
Hope it helps, othervice please refere to documentation and recent
lkml-threads.
Anders Fugmann
Samuel T Ting wrote:
> Hello all,
>
> Lately, I have been hearing a lot about preemptive kernels on the list.
> I have just started looking into kernel internals, so could somebody
> explain what kernel preemption is?
>
> Also, how does virtual memory management in 2.4.9 work?
>
> Thanks!
>
> Samuel Ting
>
> -
> 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/
>
>
prev parent reply other threads:[~2001-09-21 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 0:19 Preemptive kernel and vm management in 2.4.9 Samuel T Ting
2001-09-21 1:42 ` Mike Fedyk
2001-09-21 8:48 ` Anders Peter 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=3BAAFECC.9060701@fugmann.dhs.org \
--to=afu@fugmann.dhs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sting@u.washington.edu \
/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