Browse files

Added 'pros and cons' section

  • Loading branch information...
1 parent b133a52 commit 32db03601e06cb21b8901ad5cb77e36de5e21d79 @skaphan committed Oct 26, 2009
Showing with 30 additions and 0 deletions.
  1. +30 −0 README
@@ -132,6 +132,36 @@ being the body of a loop, that you don't know how many times is going to be
executed. Only information in the shared segments is managed transactionally.
+Here are some pros and cons of this approach:
+* Very easy to use
+* Avoids accidental memory sharing in threads
+* If number of processes <= number of cores, no worries about scheduling overhead
+* No extra code executed on memory reads and writes, except the first access to
+ each page during a transaction.
+* Enables STM in C-like languages
+* Can be a little tricky to do the right thing with non-transactionally controlled
+ data in the body of a transaction -- until you "get it."
+* Coarse grain approach -- pages supported by OS -- leads to more retried transactions
+ because of more contention.
+* If number of proceses > number of cores, scheduling overhead more significant
+ than thread-based approach.
+* System call overhead in mmap() is non-trivial.
+* Requires language such as C/C++ in which memory and file-mapped pages are directly
+ accessible.
+* Debuggers may have a hard time dealing with a program that depends on SIGBUS to
+ work at all!

0 comments on commit 32db036

Please sign in to comment.