From: Jan Kara <jack@suse.cz>
To: Jan Blunck <jblunck@suse.de>
Cc: Christoph Hellwig <hch@lst.de>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Linux-Kernel Mailinglist <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC 0/2] readdir() as an inode operation
Date: Tue, 30 Oct 2007 16:26:04 +0100 [thread overview]
Message-ID: <20071030152604.GC27039@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20071020100903.717837398@X40.localnet>
> This is a first try to move readdir() to become an inode operation. This is
> necessary for a VFS implementation of "something like union-mounts" where a
> readdir() needs to read the directory contents of multiple directories.
> Besides that the new interface is no longer giving the struct file to the
> filesystem implementations anymore.
>
> Comments, please?
Hmm, are you sure there are no users which keep some per-struct-file
information for directories? File offset is one such obvious thing which
you've handled but actually filesystem with more complicated structure
of directory may remember some hints about where we really are, keep
some readahead information or so...
Honza
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
next prev parent reply other threads:[~2007-10-30 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 10:09 [RFC 0/2] readdir() as an inode operation Jan Blunck
2007-10-20 10:09 ` [RFC 1/2] i_op->readdir: Change readdir() to be " Jan Blunck
2007-10-20 10:09 ` [RFC 2/2] i_op->readdir: Change libfs users to the new interface Jan Blunck
2007-10-30 15:26 ` Jan Kara [this message]
2007-10-31 3:43 ` [RFC 0/2] readdir() as an inode operation Brad Boyer
2007-10-31 7:13 ` Theodore Tso
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=20071030152604.GC27039@atrey.karlin.mff.cuni.cz \
--to=jack@suse.cz \
--cc=hch@lst.de \
--cc=jblunck@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).