unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Subject: Re: Resizing hash tables in Guile
Date: Wed, 12 Feb 2003 14:44:18 -0600	[thread overview]
Message-ID: <877kc5ns9p.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <xy74r792xx7.fsf@nada.kth.se> (Mikael Djurfeldt's message of "Wed, 12 Feb 2003 18:47:48 +0100")

Mikael Djurfeldt <djurfeldt@nada.kth.se> writes:

> I agree.  When implementing the current thread safety I've
> encountered a cluster of very interesting problems.  I'll write up a
> small text about this, put in the workbook and post on the list.
> I'd say I can do this within a few weeks.  For example, I've
> discovered that the with-mutex construct we provide in threads.scm
> is of dubious utility.  It also seems hard to second-guess the
> "users" needs when trying to provide high-level thread-safety
> constructs in general.

Sorry I haven't had a chance to comment sooner, but I also feel that
we should probably let the user handle thread-safety.

Way back when I first started programming heavily with threads, I had
the naive impression that everything should "just be thread safe" :>
After a lot of hacking, I would have to say I was definitively wrong.
In my experience, the issues surrounding thread-safety and the
tradeoffs involved are too complex to be easily managed in a blanket
way.  As a trivial example, it can be frustrating if you're trying to
get high performance for a segment of code, to have no way to avoid
hundreds or thousands of mutex grabs when you already *know* that the
code segment in question is protected by some other means.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


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


  reply	other threads:[~2003-02-12 20:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.3.96.1030208160743.22945E-100000@anh>
     [not found] ` <87lm0o7951.fsf@alice.rotty.yi.org>
     [not found]   ` <rmiu1fcnrhj.fsf@fnord.ir.bbn.com>
     [not found]     ` <1044889242.1033.310.camel@localhost>
     [not found]       ` <xy77kc8krhr.fsf@nada.kth.se>
     [not found]         ` <xy74r7ckqmy.fsf@nada.kth.se>
2003-02-11 13:59           ` Resizing hash tables in Guile Mikael Djurfeldt
2003-02-11 17:34             ` Roland Orre
     [not found]               ` <ljy94lhgkb.fsf@burns.dt.e-technik.uni-dortmund.de>
2003-02-12 17:47                 ` Mikael Djurfeldt
2003-02-12 20:44                   ` Rob Browning [this message]
2003-02-12 16:10             ` Marius Vollmer
2003-02-12 17:53               ` Mikael Djurfeldt
2003-02-12 20:17                 ` Roland Orre
2003-02-13  9:35                   ` Mikael Djurfeldt
2003-02-13 13:55                     ` Harvey J. Stein
2003-02-13 14:24                       ` Joris van der Hoeven
2003-02-13 18:30                         ` Harvey J. Stein
2003-02-13 20:02                           ` Paul Jarc
2003-02-13  9:52                   ` Joris van der Hoeven
2003-02-12 20:55             ` Rob Browning
2003-02-13 10:43               ` Mikael Djurfeldt

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=877kc5ns9p.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=marius.vollmer@uni-dortmund.de \
    /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).