From: Philippe Anel <xigh@bouyapop.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9vx, kproc and *double sleep*
Date: Fri, 11 Jun 2010 16:54:36 +0200 [thread overview]
Message-ID: <4C124E2C.7010008@bouyapop.org> (raw)
In-Reply-To: <f398e344c84e5946e0189ebb69638d57@kw.quanstro.net>
I don't think either splhi fixes the problem ... it only hides it for
the 99.999999999% cases.
Phil;
erik quanstrom wrote:
>> schedinit only runs once and sleep runs all the time. That's the part
>> I don't get.
>>
>
> gotolabel in sleep sends you back to the
> setlabel at the top of schedinit.
>
>
>> But you might have found something, I sure wish I understood it all better :-)
>>
>
> i'm not entirely convinced that the problem isn't the fact that splhi()
> doesn't do anything.
>
> here's what i wonder:
> - does richard miller's alternate implementation of wakeup
> solve this problem.
> - does changing spl* to manipulation of a per-cpu lock solve the problem?
> sometimes preventing anything else from running on your mach is
> exactly what you want.
>
> in any event, given the long history with sleep/wakeup, changes should
> be justified with a promula model. the current model omits the spl*
> and the second lock. (http://swtch.com/spin/sleep_wakeup.txt).
>
> - erik
>
>
>
next prev parent reply other threads:[~2010-06-11 14:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 14:06 Philippe Anel
2010-06-11 14:40 ` ron minnich
2010-06-11 14:49 ` erik quanstrom
2010-06-11 14:54 ` Philippe Anel [this message]
2010-06-11 15:03 ` erik quanstrom
2010-06-11 15:22 ` Philippe Anel
2010-06-11 15:25 ` Philippe Anel
2010-06-11 14:59 ` Philippe Anel
2010-06-11 17:11 ` Bakul Shah
2010-06-11 17:31 ` Philippe Anel
2010-06-11 18:34 ` Bakul Shah
2010-06-11 18:36 ` erik quanstrom
2010-06-11 18:51 ` Philippe Anel
2010-06-12 7:02 ` Philippe Anel
2010-06-12 9:22 ` Philippe Anel
2010-06-12 11:51 ` erik quanstrom
2010-06-13 13:01 ` Richard Miller
2010-06-13 13:43 ` Philippe Anel
2010-06-13 14:26 ` Philippe Anel
2010-06-13 16:20 ` ron minnich
2010-06-13 16:34 ` Philippe Anel
2010-06-13 17:23 ` Philippe Anel
2010-06-13 18:03 ` Philippe Anel
2010-06-14 19:15 ` Charles Forsyth
2010-06-14 19:36 ` Philippe Anel
2010-06-15 2:57 ` ron minnich
2010-06-15 3:36 ` ron minnich
2010-06-12 20:15 ` Richard Miller
2010-06-12 20:30 ` ron minnich
2010-06-12 22:15 ` Charles Forsyth
2010-06-13 0:04 ` ron minnich
2010-06-13 13:32 ` erik quanstrom
2010-06-13 22:34 ` Charles Forsyth
2010-06-13 9:00 ` Richard Miller
2010-06-11 14:49 ` Philippe Anel
2010-06-11 14:59 ` ron minnich
2010-06-11 15:02 ` ron minnich
2010-06-11 15:04 ` erik quanstrom
2010-06-11 15:43 ` ron minnich
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=4C124E2C.7010008@bouyapop.org \
--to=xigh@bouyapop.org \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).