From: Con Kolivas <kernel@kolivas.org>
To: jesse <jessezx@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Gurus, a silly question for preemptive behavior
Date: Tue, 21 Dec 2004 16:59:51 +1100 [thread overview]
Message-ID: <cone.1103608791.326982.28853.502@pc.kolivas.org> (raw)
In-Reply-To: <20041221024347.3004.qmail@web52606.mail.yahoo.com>
jesse writes:
>
> As i know, in linux, user space application is
> preemptive at any time. however, linux kernel is NOT
> preemptive, that means, even some event is finished,
> Linux kernel scheduler itself still can't have
> opportunity to interrupt the current user application
> and switch it out. it is called scheduler latency.
The kernel is preemptible if you enable the preempt option in the
configuration. There are some code paths that are not preemptible despite
this, but they are gradually being improved over time.
> normally , the latency is about 88us in mean , maximum
> : 200ms. Thus, the short latency shouldn't impact user
> applications too much and is not a problem. It is an
> issue in those embedded voice processing systems by
> introducing jitters, thus smart people came up with
> two kernel schedule patch: preemptive patch and low
> latency patch.
You're thinking about the 2.4 kernel. 2.6 is effectively both of those
patches inclusive.
> my system:
> [root@sa-c2-7 proc]# uname -a
> Linux sa-c2-7 2.4.21-15.ELsmp #1 SMP Thu Apr 22
> 00:18:24 EDT 2004 i686 i686 i386 GNU/Linux
If you want lower latency on a 2.4 kernel you need further patches. You are
most likely to benefit from a move to a 2.6 kernel and enabling preempt.
Cheers,
Con
next prev parent reply other threads:[~2004-12-21 6:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 2:43 jesse
2004-12-21 5:59 ` Con Kolivas [this message]
2004-12-21 18:32 ` jesse
2004-12-21 18:44 ` Paulo Marques
2004-12-21 19:03 ` jesse
2004-12-21 19:23 ` Paulo Marques
2004-12-21 21:35 ` Con Kolivas
2004-12-21 23:07 ` jesse
2004-12-22 2:16 ` Con Kolivas
2004-12-22 12:39 ` K.R. Foley
2004-12-26 19:30 ` Stephen Satchell
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=cone.1103608791.326982.28853.502@pc.kolivas.org \
--to=kernel@kolivas.org \
--cc=jessezx@yahoo.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
all inboxes | Powered by JetHome®