All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagi@grimberg.me>
To: Danil Kipnis <danil.kipnis@cloud.ionos.com>,
	linux-rdma@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [RFC] Reliable Multicast on top of RTRS
Date: Thu, 3 Sep 2020 15:18:43 -0700	[thread overview]
Message-ID: <5438d63e-0879-1d7b-cac1-f20fa24ecedb@grimberg.me> (raw)
In-Reply-To: <CAHg0Huzvhg7ZizbCGQyyVNdnAWmQCsypRWvdBzm0GWwPzXD0dw@mail.gmail.com>


> Hi @,
> 
> RTRS allows for reliable transmission of sg lists between two hosts
> over rdma. It is optimised for block io. One can implement a client
> and a server module on top of RTRS which would allow for reliable
> transmission to a group of hosts.
> 
> In the networking world this is called reliable multicast. I think one
> can say that reliable multicast is an equivalent to what is called
> "mirror" in the storage world.

md-raid1

> There is something called XoR network
> coding which seems to be an equivalent of raid5.

md-raid5

> There is also Reed
> Solomon network coding.
> 
> Having a reliable multicast with coding rdma-based transport layer
> would allow for very flexible and scalable designs of distributed
> replication solutions based on different in-kernel transport, block
> and replication drivers.
> 
> What do you think?

You should probably use the device-mapper stack or modify it to fit your
needs.

  parent reply	other threads:[~2020-09-03 22:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02  8:04 [RFC] Reliable Multicast on top of RTRS Danil Kipnis
2020-09-02 23:07 ` Bart Van Assche
2020-09-04 11:35   ` Danil Kipnis
2020-09-04 15:33     ` Bart Van Assche
2020-09-09 11:42       ` Danil Kipnis
2020-09-13 14:51         ` Bart Van Assche
2020-09-27  0:03         ` Bart Van Assche
2020-11-20  9:11           ` Danil Kipnis
2020-11-22 16:16       ` Danil Kipnis
2022-11-21 13:57         ` Haris Iqbal
2022-12-21  9:57           ` danil.kipnis
2020-09-03 22:18 ` Sagi Grimberg [this message]
2020-11-22 16:08   ` Danil Kipnis

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=5438d63e-0879-1d7b-cac1-f20fa24ecedb@grimberg.me \
    --to=sagi@grimberg.me \
    --cc=danil.kipnis@cloud.ionos.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.