From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Yuxin Ren <ryx@gwmail.gwu.edu>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: RCU consistency guarantees
Date: Fri, 6 Dec 2019 05:49:09 -0500 (EST) [thread overview]
Message-ID: <194534011.751.1575629349181.JavaMail.zimbra__43626.0490723484$1575629380$gmane$org@efficios.com> (raw)
In-Reply-To: <CAAKbDrdMRrhnSzpPBZLf3nNUDW4YZLPkZkTD5gNJu+A9rATkWA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1662 bytes --]
----- On Dec 5, 2019, at 8:17 PM, Yuxin Ren <ryx@gwmail.gwu.edu> wrote:
> Hi,
> I am a student, and learning RCU now, but still know very little about it.
> Are there any documents/papers/materials which (in)formally define and explain
> RCU consistency guarantees?
You may want to have a look at
User-Level Implementations of Read-Copy Update
Article in IEEE Transactions on Parallel and Distributed Systems 23(2):375 - 382 · March 2012
as a starting point.
Thanks,
Mathieu
> I know there are some consistency models in the database area (such as PRAM,
> Read Uncommitted, etc) from [ https://jepsen.io/consistency |
> https://jepsen.io/consistency ] and [1].
> How does RCU related to those consistency models?
> I also found some comments online (One key distinction is that both MVCC and RLU
> provide much stronger consistency guarantees to readers than does RCU ...) ( [
> https://lwn.net/Articles/777036/ | https://lwn.net/Articles/777036/ ] ).
> I do not understand how we reason/dresibe/compare the consistency guarantees. (
> I even do not know what consistency guarantees provided by RCU formally)
> Could someone explain this to me?
> [1] Bailis, P., Davidson, A., Fekete, A., Ghodsi, A., Hellerstein, J. M., &
> Stoica, I. (2013). Highly available transactions: Virtues and limitations.
> Proceedings of the VLDB Endowment, 7(3), 181-192.
> Thanks
> Yuxin
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
[-- Attachment #1.2: Type: text/html, Size: 3173 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next parent reply other threads:[~2019-12-06 10:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAKbDrdMRrhnSzpPBZLf3nNUDW4YZLPkZkTD5gNJu+A9rATkWA@mail.gmail.com>
2019-12-06 10:49 ` Mathieu Desnoyers [this message]
[not found] ` <194534011.751.1575629349181.JavaMail.zimbra@efficios.com>
2019-12-06 14:51 ` RCU consistency guarantees Yuxin Ren
[not found] ` <CAAKbDreZ8NerP-jsxezOmN3rktVSAk1a=RJw2YQY83UpQRrXfQ@mail.gmail.com>
2019-12-06 15:59 ` Mathieu Desnoyers
[not found] ` <512711764.1078.1575647945136.JavaMail.zimbra@efficios.com>
2019-12-06 16:30 ` Paul E. McKenney
[not found] ` <20191206163052.GG2889@paulmck-ThinkPad-P72>
2019-12-07 0:00 ` Yuxin Ren
[not found] ` <CAAKbDrfzbaPJcKQE7wsjPCgmxUMhcZshDptt=abtufbtCMp85g@mail.gmail.com>
2019-12-07 6:37 ` Paul E. McKenney
[not found] ` <20191207063730.GN2889@paulmck-ThinkPad-P72>
2019-12-07 20:04 ` Yuxin Ren
[not found] ` <CAAKbDre3N=RwTNeAqbr3MaA+zuioriLFasd85ZJsFr_pG_VApw@mail.gmail.com>
2019-12-07 22:42 ` Paul E. McKenney
[not found] ` <20191207224232.GR2889@paulmck-ThinkPad-P72>
2019-12-14 6:31 ` Yuxin Ren
[not found] ` <CAAKbDrd5s06mnPYU_dwO1+dtySewm80ukaaEqJiJ0RtkFe-38w@mail.gmail.com>
2019-12-15 20:30 ` Paul E. McKenney
[not found] ` <20191215203019.GN2889@paulmck-ThinkPad-P72>
2019-12-15 22:10 ` Yuxin Ren
[not found] ` <CAAKbDrfUGrL=Yz=mf4B1Wij3XkxgTwY-4HNB4+XJKdRGK1T2BQ@mail.gmail.com>
2019-12-16 0:57 ` Paul E. McKenney
2019-12-06 1:17 Yuxin Ren
-- strict thread matches above, loose matches on Subject: below --
2019-12-06 1:15 Yuxin Ren
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='194534011.751.1575629349181.JavaMail.zimbra__43626.0490723484$1575629380$gmane$org@efficios.com' \
--to=mathieu.desnoyers@efficios.com \
--cc=lttng-dev@lists.lttng.org \
--cc=ryx@gwmail.gwu.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;
as well as URLs for NNTP newsgroup(s).