From: "NAGABHUSHAN BS" <bsn.0007@gmail.com>
To: "Jan Blunck" <jblunck@suse.de>
Cc: libc-alpha@sourceware.org, "Erez Zadok" <ezk@cs.sunysb.edu>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
viro@zeniv.linux.org.uk, "Christoph Hellwig" <hch@lst.de>,
"Ulrich Drepper" <drepper@redhat.com>,
"Mingming Cao" <cmm@us.ibm.com>,
"Dave Hansen" <haveblue@us.ibm.com>,
"Trond Myklebust" <trond.myklebust@fys.uio.no>,
bharata@linux.vnet.ibm.com,
"David Woodhouse" <dwmw2@infradead.org>
Subject: Re: [RFC PATCH 0/2] Union Mount: Directory listing in glibc
Date: Wed, 30 Apr 2008 11:48:06 +0530 [thread overview]
Message-ID: <c810d5090804292318h41336e30n7819f2f0ea0e5a7c@mail.gmail.com> (raw)
In-Reply-To: <20080429160431.GY30780@bolzano.suse.de>
On Tue, Apr 29, 2008 at 9:34 PM, Jan Blunck <jblunck@suse.de> wrote:
> On Tue, Apr 29, bsn.0007@gmail.com wrote:
>
> > The RFC discussed about the information glibc readdir needs to get about
> > union mounted directories and I have assumed the following information
> > to be available from the kernel for this implementation.
> >
> > - Kernel would return all the dirents (including duplicates and whiteouts)
> > starting from the topmost directory of the union.
> >
> > - Indication that this directory is a union mounted directory
> > I have assumed that kernel would return a "." whiteout as the first
> > directory entry of the union. This would tell glibc readdir(3) that it is
> > working with a union mounted directory and it needs to do duplicate
> > elimination and whiteout suppression. It starts building a dirent cache
> > for this purpose.
>
> IIRC the intention was to emit a "." whiteout when "changing" from one
> directory to the next. That means when the first directory is completely read
> the whiteout is emitted. After that glibc knows to start duplicate
> removal.
>
Yes the intention was to get a "." whiteout when changing from one
directory to next and thats essentially what i have assumed, for
starting duplicate elimination.
Along with that i have also assumed to get a "." whiteout as the first
directory entry of the union, so as to indicate to glibc that the
directory is a union mounted directory.
Regards
Nagabhushan
prev parent reply other threads:[~2008-04-30 6:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 13:32 [RFC PATCH 0/2] Union Mount: Directory listing in glibc bsn.0007
2008-04-29 13:33 ` [RFC PATCH 1/2] Union Mount: glibc readdir support bsn.0007
2008-05-01 6:08 ` Ulrich Drepper
2008-05-06 4:21 ` Bharata B Rao
2008-05-06 5:46 ` hooanon05
2008-05-06 13:10 ` David Newall
2008-05-12 3:43 ` Bharata B Rao
2008-05-12 3:49 ` Erez Zadok
2008-05-09 20:05 ` Erez Zadok
2008-04-29 13:34 ` [RFC PATCH 2/2] Union Mount: glibc seekdir support bsn.0007
2008-04-29 15:21 ` [RFC PATCH 0/2] Union Mount: Directory listing in glibc hooanon05
2008-04-29 16:12 ` Jan Blunck
2008-04-29 15:49 ` Erez Zadok
2008-04-29 16:16 ` Jan Blunck
2008-04-30 6:07 ` NAGABHUSHAN BS
2008-04-30 16:35 ` Erez Zadok
2008-05-01 1:39 ` hooanon05
2008-04-29 16:04 ` Jan Blunck
2008-04-30 6:18 ` NAGABHUSHAN BS [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=c810d5090804292318h41336e30n7819f2f0ea0e5a7c@mail.gmail.com \
--to=bsn.0007@gmail.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=drepper@redhat.com \
--cc=dwmw2@infradead.org \
--cc=ezk@cs.sunysb.edu \
--cc=haveblue@us.ibm.com \
--cc=hch@lst.de \
--cc=jblunck@suse.de \
--cc=libc-alpha@sourceware.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
--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).