From: Al Viro <viro@zeniv.linux.org.uk>
To: Theodore Ts'o <tytso@mit.edu>
Cc: 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: Thu, 16 Jan 2025 16:53:21 +0000 [thread overview]
Message-ID: <20250116165321.GH1977892@ZenIV> (raw)
In-Reply-To: <20250116124949.GA2446417@mit.edu>
On Thu, Jan 16, 2025 at 07:49:49AM -0500, Theodore Ts'o wrote:
> Secondly, we've had a very long time to let the dentry interface
> mature, and so (a) the fundamental architecture of the dcache hasn't
> been changing as much in the past few years, and (b) we should have
> enough understanding of the interface to understand where we could put
> tracepoints (e.g., close to the syscall interface) which would make it
> much less likely that there would be any need to make
> backwards-incompatible changes to tracepoints.
FWIW, earlier this week I'd been going through the piles of tracepoints
playing with ->d_name. Mature interface or not, they do manage to
fuck that up...
next prev parent reply other threads:[~2025-01-16 16:53 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 [this message]
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
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=20250116165321.GH1977892@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=bpf@vger.kernel.org \
--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