From: Dan Williams <dan.j.williams@intel.com>
To: Song Liu via Lsf-pc <lsf-pc@lists.linux-foundation.org>,
Vishnu ks <ksvishnu56@gmail.com>
Cc: <hch@infradead.org>, <yanjun.zhu@linux.dev>,
<lsf-pc@lists.linux-foundation.org>,
<linux-block@vger.kernel.org>, <bpf@vger.kernel.org>,
<linux-nvme@lists.infradead.org>
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] Improving Block Layer Tracepoints for Next-Generation Backup Systems
Date: Mon, 6 Jan 2025 14:18:01 -0800 [thread overview]
Message-ID: <677c56994576b_f58f29445@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <CAPhsuW6W=08Vf=W6GZ9DCzwu4wq_AgNOayo50vxvqFMr9CcDcg@mail.gmail.com>
Song Liu via Lsf-pc wrote:
> On Sat, Jan 4, 2025 at 9:52 AM Vishnu ks <ksvishnu56@gmail.com> wrote:
> >
> [...]
> >
> > @Song: Our approach fundamentally differs from md/raid in several ways:
> >
> > 1. Network-based vs Local:
> > - Our system operates over network, allowing replication across
> > geographically distributed systems
> > - md/raid works only with locally attached storage devices
>
> md-cluster (https://docs.kernel.org/driver-api/md/md-cluster.html)
> does support RAID in a cluster.
Also,
https://docs.kernel.org/admin-guide/blockdev/drbd/index.html
next prev parent reply other threads:[~2025-01-06 22:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 6:34 [LSF/MM/BPF TOPIC] Improving Block Layer Tracepoints for Next-Generation Backup Systems Vishnu ks
2025-01-03 9:26 ` Christoph Hellwig
2025-01-04 0:47 ` Zhu Yanjun
2025-01-04 1:11 ` Song Liu
2025-01-04 17:52 ` Vishnu ks
2025-01-06 1:53 ` Damien Le Moal
2025-01-06 18:28 ` Vishnu ks
2025-01-06 7:37 ` Christoph Hellwig
2025-01-06 14:39 ` Zhu Yanjun
2025-01-06 18:36 ` Vishnu ks
2025-01-06 18:31 ` Vishnu ks
2025-01-06 21:19 ` Song Liu
2025-01-06 22:18 ` Dan Williams [this message]
2025-01-13 17:31 ` [Lsf-pc] " Vishnu ks
2025-02-07 2:06 ` Ming Lei
2025-02-07 11:15 ` Vishnu ks
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=677c56994576b_f58f29445@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=bpf@vger.kernel.org \
--cc=hch@infradead.org \
--cc=ksvishnu56@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=yanjun.zhu@linux.dev \
/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