From: Dave Jones <davej@codemonkey.org.uk>
To: Robert Love <rml@tech9.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: yet another update to the post-halloween doc.
Date: Wed, 6 Nov 2002 16:53:27 +0000 [thread overview]
Message-ID: <20021106165327.GA11290@suse.de> (raw)
In-Reply-To: <1036599481.3405.1080.camel@phantasy>
On Wed, Nov 06, 2002 at 11:18:01AM -0500, Robert Love wrote:
> One idea: how about covering new system calls? We have the thread calls
> Ingo did, the sched_[set|get]affinity calls, AIO, etc.
I've toyed with this idea, but wondered if perhaps a seperate
document would be a better idea. Ie, keep this one as a
end-users guide, and have a seperate programmers guide
covering things like API changes and the likes.
The latter would likely be more time consuming than the former,
we'll see how things go..
> > - Note, there are still cases where preemption must be temporarily disabled
> > where we do not. If you get "xxx exited with preempt count=n" messages
> > in syslog, don't panic, these are non fatal, but are somewhat unclean.
> I just want to clarify that, in the second point, the "xxx exited with
> preempt_count=n" message and not disabling preemption are two different
> issues.
Good point, that was confusing. Cleaned up.
> Not disabling preemption where needed is like an SMP race condition.
> There may be a some per-CPU data left that needs explicit protection but
> hopefully not much.
Wasn't there also some issue in various drivers ? I believe Alan cited
the 8390 net driver as one example.
> Just a note that the tree Rik and I are hacking on is the original and
> not a fork. It is the same tree mkj created and is in the official Red
> Hat CVS repository. It just has not had much activity lately and now it
> has new blood :)
>
> Albert's tree is a fork.
*sigh* politics. I changed that text after Albert mailed me complaining
about the original. Something tells me I'm not going to be able to
please both of you. I'll mangle it again, and see which one of you
complains next time 8-)
All other suggestions added/changed/etc.
Thanks for the feedback
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
next prev parent reply other threads:[~2002-11-06 16:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 14:08 yet another update to the post-halloween doc Dave Jones
2002-11-06 14:37 ` Jaroslav Kysela
2002-11-06 15:02 ` Dave Jones
2002-11-06 16:11 ` Adam Belay
2002-11-07 2:28 ` bill davidsen
2002-11-06 14:44 ` Miles Bader
2002-11-06 17:29 ` Geert Uytterhoeven
2002-11-06 15:18 ` Martin Josefsson
2002-11-06 15:23 ` Alan Cox
2002-11-06 16:18 ` Robert Love
2002-11-06 16:53 ` Dave Jones [this message]
2002-11-06 21:56 ` Robert Love
2002-11-07 16:33 ` Bill Davidsen
2002-11-07 18:18 ` Robert Love
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=20021106165327.GA11290@suse.de \
--to=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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