From: Keith Busch <kbusch@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Haris Iqbal <haris.iqbal@ionos.com>,
lsf-pc@lists.linux-foundation.org, linux-block@vger.kernel.org,
Jia Li <jia.li@ionos.com>
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] A block level, active-active replication solution
Date: Sat, 2 May 2026 12:41:41 +0100 [thread overview]
Message-ID: <afXi9crQyOnqJ4-1@kbusch-mbp> (raw)
In-Reply-To: <afUDV3ue45-shCNU@casper.infradead.org>
On Fri, May 01, 2026 at 08:47:35PM +0100, Matthew Wilcox wrote:
> On Tue, Feb 03, 2026 at 04:09:59PM +0100, Haris Iqbal via Lsf-pc wrote:
> > We are working on a pair of kernel modules which would offer a new
> > replication solution in the Linux kernel. It would be a block level,
> > active-active replication solution for RDMA transport.
>
> Why is active-active a good idea?
>
> With an active-passive solution, network traffic is directed to the
> active node. Over time at some point we get close to saturating the
> link and performance drops. At that point, human intervention will
> occur and the network link will be upgraded.
>
> With an active-active solution, traffic goes to each node. At smoe point
> each link will be about 75% utilised and we won't see any performance
> problems. But then a node goes down and all of a sudden the remaining
> node is being hit with 150% of the link capacity. There's no gradual
> degradation here; the whole solution just goes down.
Maybe I'm out of touch with reality, but I could swear active-passive
setups are often configured such that the passive node for one resource
is the active node for another. That would also suffer the same link
capacity issues you're describing.
next prev parent reply other threads:[~2026-05-02 11:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 15:09 [LSF/MM/BPF TOPIC] A block level, active-active replication solution Haris Iqbal
2026-02-03 18:01 ` Bart Van Assche
2026-02-03 18:04 ` Haris Iqbal
2026-02-10 13:06 ` Haris Iqbal
2026-02-10 18:31 ` Bart Van Assche
2026-02-13 14:13 ` Haris Iqbal
2026-02-13 17:32 ` Bart Van Assche
2026-02-19 10:43 ` Haris Iqbal
2026-04-29 14:26 ` Haris Iqbal
2026-05-01 19:47 ` [Lsf-pc] " Matthew Wilcox
2026-05-02 11:41 ` Keith Busch [this message]
2026-05-04 8:24 ` Haris Iqbal
2026-05-05 9:19 ` Philipp Reisner
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=afXi9crQyOnqJ4-1@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=haris.iqbal@ionos.com \
--cc=jia.li@ionos.com \
--cc=linux-block@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox