unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Hans Aberg <haberg-1@telia.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: Abandon lock-based synchronization in favor of STM?
Date: Fri, 24 Feb 2012 22:58:45 +0100	[thread overview]
Message-ID: <AA8508CF-E544-49FB-B5B9-CBAD860788EA@telia.com> (raw)
In-Reply-To: <87aa48ypo5.fsf@netris.org>

On 24 Feb 2012, at 20:52, Mark H Weaver wrote:

> I posted this link to IRC, but for the benefit of others, here's a paper
> that I highly recommend for anyone interested in a better way to handle
> sychronization and concurrency:
> 
> http://research.microsoft.com/en-us/um/people/simonpj/papers/stm/stm.pdf

Also described here:
  https://en.wikipedia.org/wiki/Software_transactional_memory

Hans





      reply	other threads:[~2012-02-24 21:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 19:52 Abandon lock-based synchronization in favor of STM? Mark H Weaver
2012-02-24 21:58 ` Hans Aberg [this message]

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=AA8508CF-E544-49FB-B5B9-CBAD860788EA@telia.com \
    --to=haberg-1@telia.com \
    --cc=guile-devel@gnu.org \
    --cc=mhw@netris.org \
    /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).