From: Christoph Hellwig <hch@infradead.org>
To: Vishnu ks <ksvishnu56@gmail.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-block@vger.kernel.org,
bpf@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [LSF/MM/BPF TOPIC] Improving Block Layer Tracepoints for Next-Generation Backup Systems
Date: Fri, 3 Jan 2025 01:26:46 -0800 [thread overview]
Message-ID: <Z3etVqYMWjh9n7s5@infradead.org> (raw)
In-Reply-To: <CAJHDoJac2Qa6QjhDFi7YZf0D05=Svc13ZQyX=92KsM7pkkVbJA@mail.gmail.com>
On Wed, Jan 01, 2025 at 12:04:56PM +0530, Vishnu ks wrote:
> - I'm developing a continuous data protection system using eBPF to
> monitor block request completions
> - The system aims to achieve reliable live data replication for block devices
> Current tracepoints present challenges in capturing the complete
> lifecycle of write operations
This is nuts. No, we don't guarantee any stability in the trace points,
and certainly not for data integrity operations.
Please make sure this never gets near any production system.
next prev parent reply other threads:[~2025-01-03 9:29 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 [this message]
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 ` [Lsf-pc] " Dan Williams
2025-01-13 17:31 ` 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=Z3etVqYMWjh9n7s5@infradead.org \
--to=hch@infradead.org \
--cc=bpf@vger.kernel.org \
--cc=ksvishnu56@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lsf-pc@lists.linux-foundation.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