Tuesday, February 12, 2019

Digest for comp.programming.threads@googlegroups.com - 2 updates in 2 topics

Horizon68 <horizon@horizon.com>: Feb 11 01:03PM -0800

Hello..
 
 
About Rust programming language..
 
I have just read the following about Rust programming language:
 
"What I'm going to discuss here is the choice made in Rust to disallow
having multiple mutable aliases to the same data (or a mutable alias
when there are active immutable aliases), even from the same thread.
This is essentially the "Read-Write lock" (RWLock) pattern, except it's
not being used in a threaded context, and the "locks" are done via
static analysis (compile time "borrow checking")."
 
Read more here:
 
https://manishearth.github.io/blog/2015/05/17/the-problem-with-shared-mutability/
 
So as you are noticing that to avoid race conditions etc. Rust is
using the Read-Write lock (RWLock) pattern , but i think this is not a
fine-grained parallelism, so with the Read-Write lock (RWLock) pattern
of Rust you are loosing fine-grained parallelism that gives
much more parallelism.
 
 
Thank you,
Amine Moulay Ramdane.
Horizon68 <horizon@horizon.com>: Feb 06 10:57AM -0800

Hello..
 
 
My Scalable RWLocks were updated to version 4.19
 
You can download them from:
 
https://sites.google.com/site/scalable68/scalable-rwlock
 
 
Thank you,
Amine Moulay Ramdane.
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to comp.programming.threads+unsubscribe@googlegroups.com.

No comments: