From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Christian Brauner <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
kernel test robot <oliver.sang@intel.com>,
Ajay Kaher <akaher@vmware.com>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] eventfs: Create dentries and inodes at dir open
Date: Tue, 16 Jan 2024 13:16:07 -0500 [thread overview]
Message-ID: <20240116131607.4b2664a9@gandalf.local.home> (raw)
In-Reply-To: <20240116131228.3ed23d37@gandalf.local.home>
On Tue, 16 Jan 2024 13:12:28 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> Maybe I can just use a hash to generate he inode numbers from the name?
> Hopefully there will be no collisions. Then I don't need the dentry
> creation at all.
Maybe I could use a hash of the address of the meta data to create the
inode number? That may be unique enough.
-- Steve
next prev parent reply other threads:[~2024-01-16 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 16:47 [PATCH] eventfs: Create dentries and inodes at dir open Steven Rostedt
[not found] ` <CAHk-=wjna5QYoWE+v3BWDwvs8N=QWjNN=EgxTN4dBbmySc-jcg@mail.gmail.com>
2024-01-16 18:12 ` Steven Rostedt
2024-01-16 18:16 ` Steven Rostedt [this message]
[not found] ` <CAHk-=wji07LQSMZuqbHFRnnaKvpQugqZ_GnCsfPvg9qJGVDujA@mail.gmail.com>
2024-01-16 18:37 ` Steven Rostedt
[not found] ` <CAHk-=wjZKo9-OE=9DA3rSnmSNWJSJTgFc3Yvrvm7476Cyn5xqQ@mail.gmail.com>
2024-01-16 19:42 ` Steven Rostedt
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=20240116131607.4b2664a9@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akaher@vmware.com \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=oliver.sang@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).