From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] devproc noteid changing for none
Date: Thu, 2 Jan 2014 18:28:37 -0500 [thread overview]
Message-ID: <83239c3d7e0996dd01d52735939ea1c8@mikro> (raw)
In-Reply-To: <d1c76daf9cd47b5a51d3320adefac3b2@felloff.net>
On Thu Jan 2 18:18:54 EST 2014, cinap_lenrek@felloff.net wrote:
> that said, just holding alarms qlock while setting up->alarm = 0
> is not enougth when you want to guarantee that no alarms will be
> delivered when the alarm(0) syscall returns. you would also need to
> remove a potentially posted alarm note from your note array and
> reset up->notepending (all under debug qlock of course).
that's true. up->nnote is not atomicly incremented. alarm is an
insideous little monster. it looks like a simple interface, but it is not.
- erik
next prev parent reply other threads:[~2014-01-02 23:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 21:17 cinap_lenrek
2014-01-02 21:22 ` erik quanstrom
2014-01-02 21:29 ` cinap_lenrek
2014-01-02 21:32 ` cinap_lenrek
2014-01-02 21:35 ` erik quanstrom
2014-01-02 21:41 ` cinap_lenrek
2014-01-02 21:43 ` erik quanstrom
2014-01-02 21:55 ` cinap_lenrek
2014-01-02 22:31 ` erik quanstrom
2014-01-02 22:47 ` erik quanstrom
2014-01-02 22:56 ` cinap_lenrek
2014-01-02 22:53 ` cinap_lenrek
2014-01-02 22:57 ` erik quanstrom
2014-01-02 23:01 ` cinap_lenrek
2014-01-02 23:04 ` erik quanstrom
2014-01-02 23:05 ` cinap_lenrek
2014-01-02 23:09 ` cinap_lenrek
2014-01-02 23:17 ` cinap_lenrek
2014-01-02 23:28 ` erik quanstrom [this message]
2014-01-03 0:23 ` erik quanstrom
2014-01-03 0:32 ` cinap_lenrek
2014-01-03 1:16 ` erik quanstrom
2014-01-03 1:23 ` cinap_lenrek
2014-01-03 1:31 ` erik quanstrom
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=83239c3d7e0996dd01d52735939ea1c8@mikro \
--to=quanstro@quanstro.net \
--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).