public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Björn Stenberg <bjst@contactor.se>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Conditions, flags and mutexes
Date: Tue, 27 Feb 2001 01:25:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.30.0102271013140.15781-100000@pm1.contactor.se> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 556 bytes --]

Is there a description somewhere that details the conceptual differences
between conditions, flags and mutexes, and why they are all implemented?
The reference manual tells me how to use them, but is short on "why".

I don't understand what conditions do that mutexes don't. Serializing
multiple threads' access to data? Mutexes can do that. Waking up several
threds at once? Fine, so why do we need mutexes then? Also, what is a flag
other than a "multi-mutex"? Why do we have mutexes if flags are a superset
of them?

Please enlighten me! :-)

/Björn

             reply	other threads:[~2001-02-27  1:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27  1:25 Björn Stenberg [this message]
2001-02-27 10:17 ` Jonathan Larmour

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=Pine.GSO.4.30.0102271013140.15781-100000@pm1.contactor.se \
    --to=bjst@contactor.se \
    --cc=ecos-discuss@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).