From: Steven Rostedt <rostedt@goodmis.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Amir Goldstein <amir73il@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH DRAFT 0/4] : Port tracefs to kernfs
Date: Wed, 31 Jan 2024 10:28:07 -0500 [thread overview]
Message-ID: <20240131102807.6a6c7b58@rorschach.local.home> (raw)
In-Reply-To: <20240131094117.7bccfe6c@gandalf.local.home>
On Wed, 31 Jan 2024 09:41:17 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> > So I went and started a draft for porting all of tracefs to kernfs in
> > the hopes that someone picks this up and finishes the work. I've gotten
> > the core of it done and it's pretty easy to do logical copy-pasta to
> > port this to eventfs as well.
>
> tracefs yes, but I'm not so sure about eventfs.
BTW, I do want to thank you for doing this. I would *love* to have
tracefs switched over to kernfs. Unfortunately, I have no time to do
it. I also don't want to lose the memory savings that is done in
eventfs.
Even if kernfs couldn't do what is needed in eventfs, I'd still be
happy if just the tracefs portion was converted over to kernfs, as long
as it treated the eventfs the same as tracefs does today.
I never really wanted to be the tracefs/eventfs maintainer. I just
needed the interface for tracing. The more generic code it can use, the
better. This is why I'm ecstatic for the simplification changes that
Linus is making.
-- Steve
next prev parent reply other threads:[~2024-01-31 15:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 13:36 [PATCH DRAFT 0/4] : Port tracefs to kernfs Christian Brauner
2024-01-31 13:36 ` [PATCH DRAFT 1/4] : tracefs: port " Christian Brauner
2024-02-01 0:37 ` kernel test robot
2024-02-01 0:37 ` kernel test robot
2024-02-01 7:01 ` kernel test robot
2024-01-31 13:36 ` [PATCH DRAFT 2/4] : trace: stash kernfs_node instead of dentries Christian Brauner
2024-01-31 13:36 ` [PATCH DRAFT 3/4] : hwlat: port struct file_operations thread_mode_fops to struct kernfs_ops Christian Brauner
2024-02-01 3:30 ` kernel test robot
2024-01-31 13:36 ` [PATCH DRAFT 4/4] : trace: illustrate how to convert basic open functions Christian Brauner
2024-01-31 14:41 ` [PATCH DRAFT 0/4] : Port tracefs to kernfs Steven Rostedt
2024-01-31 15:28 ` Steven Rostedt [this message]
2024-01-31 14:59 ` James Bottomley
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=20240131102807.6a6c7b58@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).