From: Brian Hurt <bhurt@spnz.org>
To: William Lovas <wlovas@stwing.upenn.edu>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] STM support in OCaml
Date: Wed, 8 Mar 2006 14:45:59 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.63.0603081438460.9569@localhost.localdomain> (raw)
In-Reply-To: <20060308193633.GA5460@coruscant.stwing.upenn.edu>
On Wed, 8 Mar 2006, William Lovas wrote:
> As the quoted paper said, though, some running transaction can always
> commit -- so not all of the associated costs are still paid. In
> particular, the cost of potential non-termination due to deadlock or
> livelock is not paid. It doesn't matter that there's a mutex under the
> hood, since it's used only in such a way as to preserve the property that
> some transaction can always complete.
One comment I will make is that a mutex is expensive, but not *that*
expensive. I just wrote a quick program (available if anyone cares) in
GNU C that measures the cost, in clocks, of locking and unlocking a posix
mutex. On my desktop box (AMD Athlon XP 2200+ 1.8GHz), I'm getting a cost
of like 44 clock cycles. Which makes it less expensive than an L2 cache
miss.
At this point correctness is a much bigger concern of mine than absolute
performance. A fair bit of conservative or unnecessary locking is
acceptable, given than I can write a complicated and highly scalable
application and know that I don't have deadlocks or livelocks. Not having
race conditions would also be nice, but I don't think that's possible with
mutable data.
Brian
next prev parent reply other threads:[~2006-03-08 20:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 16:18 Asfand Yar Qazi
2006-03-07 16:50 ` [Caml-list] " Sebastian Egner
2006-03-07 17:44 ` Michael Hicks
2006-03-08 0:37 ` Asfand Yar Qazi
2006-03-08 5:05 ` Erick Tryzelaar
2006-03-11 19:43 ` Deadlock free locking scheme (was: Re: [Caml-list] STM support in OCaml) David MENTRE
2006-03-07 17:15 ` [Caml-list] STM support in OCaml skaller
2006-03-07 19:05 ` Asfand Yar Qazi
2006-03-08 0:52 ` skaller
2006-03-08 7:08 ` Bardur Arantsson
2006-03-08 10:38 ` [Caml-list] " Asfand Yar Qazi
2006-03-08 19:36 ` William Lovas
2006-03-08 20:45 ` Brian Hurt [this message]
2006-03-08 21:14 ` Paul Snively
2006-03-08 22:06 ` skaller
2006-03-08 22:10 ` Gerd Stolpmann
2006-03-08 23:48 ` skaller
2006-03-09 7:45 ` Andrae Muys
2006-03-09 9:18 ` David Brown
2006-03-08 22:11 ` Brian Hurt
2006-03-08 23:05 ` Lodewijk Vöge
2006-03-09 3:13 ` Brian Hurt
2006-03-08 23:45 ` Robert Roessler
2006-03-09 0:23 ` skaller
2006-03-09 3:19 ` Brian Hurt
2006-03-09 4:32 ` skaller
2006-03-09 10:38 ` John Chu
2006-03-09 16:53 ` Stefan Monnier
2006-03-11 15:26 ` [Caml-list] " Florian Weimer
2006-03-08 10:11 yoann padioleau
2006-03-08 10:41 ` Asfand Yar Qazi
2006-03-08 12:23 ` skaller
2006-03-08 23:02 ` Asfand Yar Qazi
2006-03-09 0:36 ` skaller
2006-03-08 11:32 ` Gerd Stolpmann
2006-03-08 12:04 ` skaller
2006-03-08 19:22 ` Dan Grossman
2006-03-08 22:10 ` skaller
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.LNX.4.63.0603081438460.9569@localhost.localdomain \
--to=bhurt@spnz.org \
--cc=caml-list@yquem.inria.fr \
--cc=wlovas@stwing.upenn.edu \
/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