From: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
ezk@cs.sunysb.edu, mhalcrow@us.ibm.com,
phillip@hellewell.homeip.net
Subject: Re: [RFC/PATCH 1/2] stackfs: generic functions for obtaining hidden object
Date: Fri, 13 Oct 2006 09:40:35 -0400 [thread overview]
Message-ID: <20061013134035.GD3936@filer.fsl.cs.sunysb.edu> (raw)
In-Reply-To: <Pine.LNX.4.64.0610131615370.563@sbz-30.cs.Helsinki.FI>
On Fri, Oct 13, 2006 at 04:22:09PM +0300, Pekka J Enberg wrote:
> From: Pekka Enberg <penberg@cs.helsinki.fi>
>
> Add generic functions for obtaining the hidden object (superblock, inode,
> dentry, and dentry mount-point) in a stacked filesystem. As fan-out
> stacked filesystems have multiple hidden objects, we store them in a
> statically allocated array of pointers. The current hard-coded limit
> STACKFS_MAX_BRANCHES is not enough for unionfs (for which users have more
> than 100 branches). That, however, can be fixed later for unionfs.
Most users have 2-3 branches, however there are few that do indeed have 100
or more branches in one Union.
The functions you have allow you to get the values out of the arrays, but
there are no set functions. Otherwise it looks good.
Acked-by: Josef "Jeff" Sipek <jsipek@cs.sunysb.edu>
--
I think there is a world market for maybe five computers.
- Thomas Watson, chairman of IBM, 1943.
next prev parent reply other threads:[~2006-10-13 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 13:22 Pekka J Enberg
2006-10-13 13:40 ` Josef Sipek [this message]
2006-10-13 15:43 ` Erez Zadok
2006-10-13 16:23 ` Pekka Enberg
2006-10-13 17:23 ` Josef Sipek
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=20061013134035.GD3936@filer.fsl.cs.sunysb.edu \
--to=jsipek@fsl.cs.sunysb.edu \
--cc=ezk@cs.sunysb.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
--cc=penberg@cs.helsinki.fi \
--cc=phillip@hellewell.homeip.net \
/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
all inboxes | Powered by JetHome®