From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, jblunck@suse.de,
dlezcano@fr.ibm.com, linux-kernel@vger.kernel.org,
viro@ZenIV.linux.org.uk
Subject: Re: [rfc git patch] union directory
Date: Mon, 1 Dec 2008 13:29:53 +0530 [thread overview]
Message-ID: <20081201075953.GE3388@in.ibm.com> (raw)
In-Reply-To: <20081201043509.GA3388@in.ibm.com>
On Mon, Dec 01, 2008 at 10:05:09AM +0530, Bharata B Rao wrote:
> On Sat, Nov 29, 2008 at 05:33:19PM +0100, Miklos Szeredi wrote:
> > On Fri, 28 Nov 2008, Bharata B Rao wrote:
> >
> > The plan is to get a simple kernel implementation first which caches
> > the directory in 'struct file'.
>
> FYI, I did this for a version of Union Mount.
> (http://lkml.org/lkml/2007/6/20/21) I was maintaining the readdir cache in
> struct file and the cache was persistant across readdir calls.
>
> Do you have anything different in mind ?
The version pointed to by me above had the entire cache stored
in the struct file of the topmost directory. I guess your plan
is to cache them per branch and combine them during
readdir()/getdents() ?
Regards,
Bharata.
next prev parent reply other threads:[~2008-12-01 8:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 11:01 [rfc git patch] union directory Miklos Szeredi
2008-11-28 16:19 ` Bharata B Rao
2008-11-29 16:33 ` Miklos Szeredi
2008-12-01 3:57 ` hooanon05
2008-12-01 4:35 ` Bharata B Rao
2008-12-01 7:59 ` Bharata B Rao [this message]
2008-12-01 19:31 ` Miklos Szeredi
2008-12-01 16:24 ` David P. Quigley
2008-12-01 16:54 ` Erez Zadok
2008-12-17 5:21 ` Ian Kent
2008-12-18 16:45 ` Miklos Szeredi
2008-12-19 1:47 ` Ian Kent
2008-12-22 13:52 ` Miklos Szeredi
2008-12-22 14:22 ` Ian Kent
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=20081201075953.GE3388@in.ibm.com \
--to=bharata@linux.vnet.ibm.com \
--cc=dlezcano@fr.ibm.com \
--cc=jblunck@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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 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.