From: Eric Van Hensbergen <ericvh@kernel.org>
To: v9fs@lists.linux.dev
Cc: Christian Schoenebeck <linux_oss@crudebyte.com>, asmadeus@codewreck.org
Subject: inodes in dirread
Date: Fri, 5 Jan 2024 12:50:57 -0600 [thread overview]
Message-ID: <ZZhPkZFWUyBXRcdo@FV7GG9FTHL> (raw)
Anyone know what the inode in dirent is actually used for during a
dirread? Right now we are hashing the qid to an inode number, but
I was planning on re-writing this so we can let the client allocate
inode numbers for itself to guarentee uniqueness. However, that
would mean I'd have to allocate inode numbers is dirread (if we aren't
using the cache) and then immediately discarding them which seems
wasteful. Puting qid.path there "works" but I'm not sure what assumptions
I'm breaking.
-eric
next reply other threads:[~2024-01-05 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 18:50 Eric Van Hensbergen [this message]
2024-01-06 1:52 ` inodes in dirread Eric Van Hensbergen
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=ZZhPkZFWUyBXRcdo@FV7GG9FTHL \
--to=ericvh@kernel.org \
--cc=asmadeus@codewreck.org \
--cc=linux_oss@crudebyte.com \
--cc=v9fs@lists.linux.dev \
/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