From: "Jakub Jermar" <jj@comberg.cz>
To: "9fans" <9fans@cse.psu.edu>
Subject: Re: [9fans] sleep(), sched() and ilock()
Date: Wed, 20 Sep 2000 07:27:42 +0200 [thread overview]
Message-ID: <007a01c022c3$d36bd340$926114d4@cz99.cz> (raw)
In-Reply-To: <05a001c04af7$0b262280$0ab9c6d4@cybercable.fr>
> multi-processor or not, a quick squiz at the lyons'
> commentary would explain a lot.
>
> you can derive a lot from first principles...
>
I am not familiar with the lyons's commentary (several days ago, I read some
bad criticism on it in 9fans), but I am pretty familiar with the principles
of interrupt and lock protecting.
I exactly know what the code is doing and what is it used for, but I can't
distinguish between the goals and the consequences (or -if you want- side
effects). Again, I don't ask about the functionality, I just want to know
what is the goal and what is the consequence.
As for the multi- versus uni-processors: there are important issues that
make the behaviour different.
As an evidence of this, you can find uni-processor branches of code that try
to avoid deadlock, which simply cannot happen on SMP (in the same
situation). A good example of what I've just said is ilock() itself.
Jakub Jermar
next prev parent reply other threads:[~2000-09-20 5:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 2:11 Russ Cox
2000-11-10 9:17 ` Boyd Roberts
2000-09-20 5:27 ` Jakub Jermar [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-10 13:06 presotto
2000-09-20 9:22 ` Jakub Jermar
2000-11-09 21:15 presotto
2000-09-20 4:35 ` Jakub Jermar
2000-09-20 2:40 Jakub Jermář
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='007a01c022c3$d36bd340$926114d4@cz99.cz' \
--to=jj@comberg.cz \
--cc=9fans@cse.psu.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;
as well as URLs for NNTP newsgroup(s).