Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: ryx@gwmail.gwu.edu (Yuxin Ren)
Subject: [lttng-dev] RCU consistency guarantees
Date: Thu, 5 Dec 2019 20:15:10 -0500	[thread overview]
Message-ID: <CAAKbDreHuNhhFE6hvz=kUBGyUw9pi=Jp=iw_T1zFMZLzfVvAxA@mail.gmail.com> (raw)

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?

I know there are some consistency models in the database area (such as
PRAM, Read Uncommitted, etc) from 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/).
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20191205/e74c3554/attachment.html>


             reply	other threads:[~2019-12-06  1:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06  1:15 Yuxin Ren [this message]
2019-12-06  1:17 Yuxin Ren
2019-12-06 10:49 ` Mathieu Desnoyers
2019-12-06 14:51   ` Yuxin Ren
2019-12-06 15:59     ` Mathieu Desnoyers
2019-12-06 16:30       ` Paul E. McKenney
2019-12-07  0:00         ` Yuxin Ren
2019-12-07  6:37           ` Paul E. McKenney
2019-12-07 20:04             ` Yuxin Ren
2019-12-07 22:42               ` Paul E. McKenney
2019-12-14  6:31                 ` Yuxin Ren
2019-12-15 20:30                   ` Paul E. McKenney
2019-12-15 22:10                     ` Yuxin Ren
2019-12-16  0:57                       ` Paul E. McKenney

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='CAAKbDreHuNhhFE6hvz=kUBGyUw9pi=Jp=iw_T1zFMZLzfVvAxA@mail.gmail.com' \
    --to=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