From: Steven Rostedt <rostedt@goodmis.org>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [LSF/MM/BPF TOPIC] Dynamic allocation of pseudo file systems
Date: Fri, 4 Mar 2022 17:56:55 -0500 [thread overview]
Message-ID: <20220304175655.055dcdde@gandalf.local.home> (raw)
At the 2021 Linux Plumbers Tracing Microconference there was a discussionon creating just-in-time dentrys for pseudo file systems (the tracing one
was about the events directory in tracefs).
https://lpc.events/event/11/contributions/1085/attachments/855/1668/Eventfs_split_v15.pdf
https://www.youtube.com/watch?v=jsxuVI7Wav0&list=PLVsQ_xZBEyN3wA8Ej4BUjudXFbXuxhnfc&t=7561s
At the microconference there was also interest in extending this to other
pseudo file systems like /sys and /proc. The rationale for this is due to
the fact that the dentrys take up a lot of memory, and there's no reason to
have them if nobody is looking at them. Having a way to create them at the
time the user looks at/enters the directory would save quite a bit. But
there may be issues. What happens if there's no memory to allocate?
Our focus was on just working with the tracefs file system, but I would
like to discuss how we could make this into a generic feature that any
pseudo file system can use, and discuss what issues could arise by it, and
how to mitigate those issues.
Sorry, for the delay in posting. I understand that the deadline has just
passed, but starting a new job had caused me to not pay attention and I
missed it. Hopefully, you can still consider this.
-- Steve
reply other threads:[~2022-03-04 22:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220304175655.055dcdde@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).