[Barrelfish-users] two phase commit (2PC ) implementation
Timothy Roscoe
troscoe at inf.ethz.ch
Fri Feb 17 08:36:45 CET 2017
Hi Yuxin,
This statement is true, except that we do not use 2PC for capability
retype at this point. Instead, every capability has a "home" node,
and operations on that capability are serialized through that node.
For the moment, that's a faster way to do it.
-- Mothy
At Fri, 17 Feb 2017 05:49:36 +0800, Yuxin Ren <ryx at gwmail.gwu.edu> wrote:
> Hi,
>
> Barrelfish implements a apability model using a local partial replica
> of the capability database on each
> core, and maintains the consistency of those replicas (for remote
> operations such as retype, revocation, etc.)
> using message-passing protocols such as 2PC.
>
> Is above statement true?
> If so, could someone provide me link to the 2PC implementation in Barrelfish?
>
> Thanks a lot!
> Yuxin
> _______________________________________________
> Barrelfish-users mailing list
> Barrelfish-users at lists.inf.ethz.ch
> https://lists.inf.ethz.ch/mailman/listinfo/barrelfish-users
>
>
>
More information about the Barrelfish-users
mailing list