From: Christian Brauner <brauner@kernel.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Dave Chinner <david@fromorbit.com>, Theodore Ts'o <tytso@mit.edu>,
lsf-pc@lists.linux-foundation.org,
Linux Filesystem Development List
<linux-fsdevel@vger.kernel.org>,
bpf@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] time to reconsider tracepoints in the vfs?
Date: Mon, 20 Jan 2025 16:42:18 +0100 [thread overview]
Message-ID: <20250120-gemieden-miene-9b22201f9844@brauner> (raw)
In-Reply-To: <CAEf4Bzbe6vWS3wvmvTcCAQY6bZf2G-D6msgvwYHyWVg3HnMXSg@mail.gmail.com>
> - relative stability of tracepoints in terms of naming, semantics,
> arguments. While not stable APIs, tracepoints are "more stable" in
> practice due to more deliberate and strategic placement (usually), so
> they tend to get renamed or changed much less frequently.
I will support tracepoints in the VFS. It would be very useful to have
them.
But we will clearly document that we retain the right to change them at
any time. Tracepoints will not become a burden for refactorings or
rewrites that tend to happen not that infrequently.
next prev parent reply other threads:[~2025-01-20 15:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 12:49 [LSF/MM/BPF TOPIC] time to reconsider tracepoints in the vfs? Theodore Ts'o
2025-01-16 16:53 ` Al Viro
2025-01-16 17:29 ` [Lsf-pc] " Jan Kara
2025-01-16 17:20 ` Jan Kara
2025-01-20 15:43 ` Christian Brauner
2025-01-20 17:15 ` Jan Kara
2025-01-16 21:18 ` Dave Chinner
2025-01-16 21:43 ` Andrii Nakryiko
2025-01-17 2:20 ` Al Viro
2025-01-17 18:33 ` Andrii Nakryiko
2025-01-20 15:42 ` Christian Brauner [this message]
2025-01-18 3:07 ` Daniel Xu
2025-01-18 3:37 ` Al Viro
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=20250120-gemieden-miene-9b22201f9844@brauner \
--to=brauner@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=tytso@mit.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