unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <mdj@kvast.blakulla.net>
Cc: djurfeldt@nada.kth.se
Subject: [pthreads] critical sections
Date: Mon, 09 Dec 2002 15:05:56 +0100	[thread overview]
Message-ID: <E18LOXk-00065d-00@linnaeus> (raw)

A few comments:

1. We should work on continuing to remove critical sections.  Several
   of the current ones aren't required.

2. For those required, we should convert them into non-recursive
   sections (SCM_NONREC_CRIT...) which is much cheaper and simpler to
   work with.

3. We should classify sections and use different mutecis so that
   totally unrelated code doesn't interfere causing serialization.

4. We should break up SCM_DEFER/ALLOW_INTS into classes.

5. Macro expansion is now completely serialized.  Is it important to
   do anything about that?  It's probably possible.

M


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


                 reply	other threads:[~2002-12-09 14:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E18LOXk-00065d-00@linnaeus \
    --to=mdj@kvast.blakulla.net \
    --cc=djurfeldt@nada.kth.se \
    /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).