From: hooanon05@yahoo.co.jp
To: "Josef 'Jeff' Sipek" <jsipek@cs.sunysb.edu>
Cc: Bharata B Rao <bharata@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
hch@infradead.org, Jan Blunck <jblunck@suse.de>
Subject: Re: [RFC] Union Mount: Readdir approaches
Date: Mon, 10 Sep 2007 11:16:43 +0900 [thread overview]
Message-ID: <E1IUYpP-0000z6-BS@jroun> (raw)
In-Reply-To: <20070907173941.GB20360@filer.fsl.cs.sunysb.edu>
Hello Jeff,
"Josef 'Jeff' Sipek":
> Unless I missunderstood something, Unionfs uses the same approach. Even
> Unionfs's ODF branch does the same thing. The major difference is that we
> keep the cache in a file on a disk.
The approach unionfs-2.1.2 took differs from mine.
Major difference is,
- in this approach, the cache in struct file is the completed virtual
disk block for the dir.
- readdir doesn't have to call vfs_readdir when the cache exists and is
valid. simply calls filldir.
- it supports SEEK_END.
Junjiro Okajima
next prev parent reply other threads:[~2007-09-10 2:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 5:46 [RFC] Union Mount: Readdir approaches Bharata B Rao
2007-09-07 7:31 ` hooanon05
2007-09-07 7:58 ` Bharata B Rao
2007-09-07 17:39 ` Josef 'Jeff' Sipek
2007-09-07 17:54 ` Erez Zadok
2007-09-10 5:15 ` Bharata B Rao
2007-09-10 2:16 ` hooanon05 [this message]
[not found] ` <20070911165547.GA26515@filer.fsl.cs.sunysb.edu>
2007-09-12 2:05 ` hooanon05
2007-09-10 3:46 ` Bharata B Rao
2007-09-07 11:54 ` Al Boldi
2007-09-07 12:49 ` hooanon05
2007-09-12 10:46 ` Al Boldi
2007-09-12 18:25 ` Jan Engelhardt
2007-09-13 2:15 ` hooanon05
2007-09-13 5:32 ` Al Boldi
2007-09-13 5:52 ` hooanon05
2007-09-13 6:29 ` Jan Engelhardt
2007-09-07 23:04 ` Matt Keenan
2007-09-10 2:17 ` hooanon05
2007-09-07 14:39 ` Jan Engelhardt
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=E1IUYpP-0000z6-BS@jroun \
--to=hooanon05@yahoo.co.jp \
--cc=bharata@linux.vnet.ibm.com \
--cc=hch@infradead.org \
--cc=jblunck@suse.de \
--cc=jsipek@cs.sunysb.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox