[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.programming

I correct some typos , please read again...

Ramine

1/31/2015 1:16:00 AM

I correct some typos , please read again...

Hello,




I want to clear something about my Distributed sequential lock
algorithm, you can download it and read about it here:

https://sites.google.com/site/aminer68/scalable-distributed-seque...


If you read carefully the source code you will notice that
i am using this: "myid3:=FCount6^.fcount6;" inside the RLock()
method in the reader side, so when my algorithm switches
from a Seqlock mode to a Distributed lock mode, the
"myid3:=FCount6^.fcount6;" will be "serialized" when the
writer side increment FCount6^.fcount6, so in the writer side i am
calling the distributed reader-writer lock when the algorithm switches
to a Distributed mode, so if you have noticed since the
"myid3:=FCount6^.fcount6;" is serialized in the reader side
when "FCount6^.fcount6" is incremented in the writer side,
so this will look like a probabilistic mechanism cause
the reader side is serializing the the transfer of FCount6^.fcount6
on the bus, and the writer side is serializing the transfer of
a variable in the bus also when it is calling the WLock() of the
distributed lock, so this is a kind of a probabilistic mechanism
cause this can generate contention and the reader side can call
RLock() on a distributed lock's reader-writer mutex that is entered
before the reader by the writer, but even though it is a probabilistic
mechanism, this probabilistic mechanism will give a good result and it
eliminates the "livelock" situation of the Seqlock when
there is more writers.




Thank you for your time.


Amine Moulay Ramdane.
2 Answers

Samuel W Flint

2/2/2015 11:16:00 PM

0

Instead of writing a new message, try using the "cancelling" feature of
your news reader. Then re-post.


--
Samuel W. Flint
"The most dangerous phrase in the language is, 'We've always done it
this way'." -- Grace Hopper

Kaz Kylheku

2/2/2015 11:53:00 PM

0

On 2015-02-02, Samuel W Flint <swflint@flintfam.org> wrote:
> Instead of writing a new message, try using the "cancelling" feature of
> your news reader. Then re-post.

That is the same thing as writing a new message.

Fixing a message is done with supersede.

Cancel and supersede aren't reliable. If your server allows them all (cesspools
like the one I'm using don't), there is no guarantee that these updates will
reach all the same places that the original reached. Then you end up with
sitautions like the original is still present in some servers and canceled in
others. (Or the old version is present in some servers and the superseded one
in others.)

It's best to treat Usenet as immutable, and follow up to your own post with
corrections. Quote the minimal amount of context necessary for the errata;
don't re-post the whole thing.

And don't put your foot in your mouth in a major way, of course.