linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] vfs generic subtree support
Date: Tue, 16 Feb 2010 12:20:29 +0000	[thread overview]
Message-ID: <20100216122029.GC30031@ZenIV.linux.org.uk> (raw)
In-Reply-To: <87tythtptw.fsf@openvz.org>

On Tue, Feb 16, 2010 at 01:52:43PM +0300, Dmitry Monakhov wrote:
> Initially i've posted RFC patch-set which add subtree support for ext4.
> http://marc.info/?l=linux-ext4&m=126563931215496&w=2
> But in fact this is rather generic feature which may be implemented 
> in vfs layer similar to namespace or security feature.
> 
> A subtree of a directory tree T is a tree consisting of a directory
> (the subtree root) in T and all of its descendants in T.
> 
> Subtree assumptions:
> * Each inode has subtree id (this id is stored inside inode).
> * Subtree id is inherent from parent directory if corresponding flag is set
> * Inode can not belongs to different subtrees
> 
> i've ommit subtree_type feature in order to simplify brief explanation.
> 
> Subtree with id == 0 has special meaning. It may contains roots of
> other subtrees (this feature is used for cross subtree renames)
> This feature has much in common with XFS project_id.

Um.  Just how is it different from having normal subtrees mounted separately?
And what's the ID for?

We already can mount arbitrary subtrees of directory tree from given fs,
as many times as we want and in as many places as we like.  With each
mountpoint acting as barrier to link() and rename().

  reply	other threads:[~2010-02-16 12:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16 10:52 [RFC] vfs generic subtree support Dmitry Monakhov
2010-02-16 12:20 ` Al Viro [this message]
2010-02-16 12:37   ` Dmitry Monakhov
2010-02-16 13:38     ` Al Viro
2010-02-16 14:01       ` Dmitry Monakhov
2010-02-16 14:21         ` Al Viro
2010-02-16 15:00           ` Dmitry Monakhov
2010-02-16 15:12             ` Matthew Wilcox
2010-02-16 15:32               ` Dmitry Monakhov
2010-02-16 19:25                 ` J. Bruce Fields
2010-02-16 19:32                   ` Christoph Hellwig
2010-02-16 19:39                     ` J. Bruce Fields

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=20100216122029.GC30031@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=dmonakhov@openvz.org \
    --cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).