From: Mark Hounschell <markh@compro.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: rt20 patch question
Date: Tue, 09 May 2006 10:58:00 -0400 [thread overview]
Message-ID: <4460ADF8.4040301@compro.net> (raw)
In-Reply-To: <1147185483.21536.13.camel@c-67-180-134-207.hsd1.ca.comcast.net>
Daniel Walker wrote:
> On Tue, 2006-05-09 at 08:23 -0400, Mark Hounschell wrote:
>> Can I assume configuring 'Complete preemption' is the same as
>> configuring ('Voluntary preemption' + 'Hardirq' + 'Softirq' + default
>> proc settings)?
>
> Not Voluntary preemption, and I'm not sure what default proc settings is
> referring too .
The proc settings or boot options to enable or disable hardirq or
softirq threading that you have avaialable in Voluntary preemption.
> Complete preemption is like CONFIG_PREEMPT and softirq
> and hardirq threading .. The preemption isn't voluntary, it's forced .
>
Complete preemption you have no choice of threading hard or soft irqs.
They are threaded.
So If I config Voluntary preemption + Hardirq and Softirq threading and
do not disable hardirq or softirq via proc or boot cmdline, is that the
same as configuring Complete preemption?
Mark
next prev parent reply other threads:[~2006-05-09 14:58 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 12:23 rt20 patch question Mark Hounschell
2006-05-09 14:38 ` Daniel Walker
2006-05-09 14:58 ` Mark Hounschell [this message]
2006-05-09 15:53 ` Daniel Walker
2006-05-10 12:39 ` Steven Rostedt
2006-05-10 13:06 ` Mark Hounschell
2006-05-10 14:10 ` Steven Rostedt
2006-05-10 15:33 ` Mark Hounschell
2006-05-10 16:17 ` Steven Rostedt
2006-05-10 18:30 ` Mark Hounschell
2006-05-10 18:49 ` Steven Rostedt
2006-05-10 19:28 ` Mark Hounschell
2006-05-11 11:25 ` Mark Hounschell
2006-05-11 12:01 ` Steven Rostedt
2006-05-11 12:22 ` Steven Rostedt
2006-05-11 13:02 ` Mark Hounschell
2006-05-11 13:14 ` Steven Rostedt
2006-05-11 13:26 ` Mark Hounschell
2006-05-11 13:53 ` Steven Rostedt
2006-05-11 14:57 ` Mark Hounschell
2006-05-12 6:47 ` Steven Rostedt
2006-05-12 7:33 ` Sébastien Dugué
2006-05-12 8:18 ` Mark Hounschell
2006-05-12 9:08 ` Mark Hounschell
2006-05-12 9:20 ` Steven Rostedt
2006-05-10 20:33 ` Steven Rostedt
2006-05-12 8:16 ` Ingo Molnar
2006-05-12 8:45 ` Steven Rostedt
2006-05-12 9:16 ` Ingo Molnar
2006-05-12 9:21 ` Ingo Molnar
2006-05-12 12:38 ` Mark Hounschell
2006-05-12 13:18 ` Steven Rostedt
2006-05-12 13:38 ` Mark Hounschell
2006-05-12 13:43 ` Mark Hounschell
2006-05-12 14:05 ` Steven Rostedt
2006-05-12 14:36 ` Mark Hounschell
2006-05-12 14:51 ` Steven Rostedt
2006-05-12 13:16 ` 3c59x vortex_timer rt hack (was: rt20 patch question) Steven Rostedt
2006-05-12 13:36 ` Ingo Molnar
2006-05-12 13:46 ` Steven Rostedt
2006-05-12 14:16 ` Andrew Morton
2006-05-12 14:32 ` Steven Rostedt
2006-05-12 14:39 ` Steven Rostedt
2006-05-12 14:43 ` Ingo Molnar
2006-05-12 14:49 ` Andrew Morton
2006-05-12 15:04 ` Steven Rostedt
2006-05-12 16:53 ` 3c59x vortex_timer rt hack Mark Hounschell
2006-05-12 15:22 ` 3c59x vortex_timer rt hack (was: rt20 patch question) Steven Rostedt
2006-05-12 15:23 ` Andrew Morton
2006-05-12 15:36 ` Steven Rostedt
2006-05-12 16:03 ` Andrew Morton
2006-05-12 16:11 ` Steven Rostedt
2006-05-12 16:27 ` Andrew Morton
2006-05-12 16:38 ` Steven Rostedt
2006-05-10 18:45 ` rt20 patch question Steven Rostedt
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=4460ADF8.4040301@compro.net \
--to=markh@compro.net \
--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;
as well as URLs for NNTP newsgroup(s).