From: Robert Love <rml@tech9.net>
To: george anzinger <george@mvista.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5: preemptive kernel on UP
Date: 06 Mar 2002 15:21:20 -0500 [thread overview]
Message-ID: <1015446092.1482.6.camel@icbm> (raw)
In-Reply-To: <3C866B56.AE2F63BD@mvista.com>
In-Reply-To: <1015287099.865.3.camel@phantasy> <3C866B56.AE2F63BD@mvista.com>
On Wed, 2002-03-06 at 14:17, george anzinger wrote:
> With out a lot of looking, wouldn't it be easier to just change fork?
Don't we need to unlock the rq regardless of what fork does?
Also, the alternative would be to set preempt_count to 0 if
CONFIG_PREEMPT and 1 if CONFIG_PREEMPT && CONFIG_SMP. I figured Linus
would balk at that sort #if/#else in do_fork. And, even then, is it
safe to start the task with a preempt_count of 0?
Robert Love
prev parent reply other threads:[~2002-03-06 20:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 0:11 [PATCH] 2.5: preemptive kernel on UP Robert Love
2002-03-05 0:43 ` Russell King
2002-03-05 0:51 ` Robert Love
2002-03-05 0:53 ` Russell King
2002-03-05 0:58 ` Robert Love
2002-03-05 1:55 ` Alan Cox
2002-03-05 1:43 ` Robert Love
2002-03-05 4:40 ` Ben Clifford
2002-03-05 1:56 ` yodaiken
2002-03-06 19:17 ` george anzinger
2002-03-06 20:21 ` Robert Love [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=1015446092.1482.6.camel@icbm \
--to=rml@tech9.net \
--cc=george@mvista.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