From: Eric Van Hensbergen <ericvh@kernel.org>
To: v9fs@lists.linux.dev
Cc: Christian Schoenebeck <linux_oss@crudebyte.com>, asmadeus@codewreck.org
Subject: Re: inodes in dirread
Date: Sat, 6 Jan 2024 01:52:39 +0000 [thread overview]
Message-ID: <ZZiyZxQ2cykCIgmj@1149290c588b> (raw)
In-Reply-To: <ZZhPkZFWUyBXRcdo@FV7GG9FTHL>
On Fri, Jan 05, 2024 at 12:50:57PM -0600, Eric Van Hensbergen wrote:
> 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.
>
Disregard, I ended up backing out that particular line of inquiry
and just sticking with the modified qid.paths in the i_ino for now.
-eric
prev parent reply other threads:[~2024-01-06 1:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 18:50 inodes in dirread Eric Van Hensbergen
2024-01-06 1:52 ` Eric Van Hensbergen [this message]
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=ZZiyZxQ2cykCIgmj@1149290c588b \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).