From: Jeff Layton <jlayton@redhat.com>
To: Kirill Korotaev <dev@sw.ru>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
dada1@cosmosbay.com, dev@openvz.org
Subject: Re: [PATCH 1/2] add lazy_getattr and lazy_readdir patches that defer i_ino assignment
Date: Tue, 30 Jan 2007 11:41:46 -0500 [thread overview]
Message-ID: <45BF754A.1030307@redhat.com> (raw)
In-Reply-To: <45BF7499.1000805@sw.ru>
Kirill Korotaev wrote:
> Jeff,
>
> taking into account the discussion about unawarness/uncertainty
> of whether *unique* inode number is needed at all on pipe fds and such
> do we need this at all?
>
> Thanks,
> Kirill
>
Fair enough, perhaps we should just not worry about it, and assume that there
might be collisions.
If so, I should probably just have Andrew withdraw the patch I submitted earlier
to hash the inodes for pipefs. I'll look at other callers of new_inode and fix
up any of the ones that need fixing.
Does that seem like the most reasonable approach?
-- Jeff
next prev parent reply other threads:[~2007-01-30 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 15:38 [PATCH 1/2] add lazy_getattr and lazy_readdir patches that defer i_ino assignment Jeff Layton
2007-01-30 16:38 ` Kirill Korotaev
2007-01-30 16:41 ` Jeff Layton [this message]
2007-01-30 17:17 ` Kirill Korotaev
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=45BF754A.1030307@redhat.com \
--to=jlayton@redhat.com \
--cc=dada1@cosmosbay.com \
--cc=dev@openvz.org \
--cc=dev@sw.ru \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.