From: Theodore Ts'o <tytso@mit.edu>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, jack@suse.cz
Subject: Re: [PATCH 2/3] ext4: Implement subtree ID support for ext4 filesystem
Date: Wed, 11 Jul 2012 09:24:29 -0400 [thread overview]
Message-ID: <20120711132429.GA10872@thunk.org> (raw)
In-Reply-To: <874npefo7n.fsf@dmbot.sw.ru>
On Wed, Jul 11, 2012 at 04:59:24PM +0400, Dmitry Monakhov wrote:
>
> May be it would be better if i describe feature as "Namespace ID"
> namespaces is well known abstraction in kernel, so misunderstanding
> shouldn't happen.
What if we call it a "quota group", with the rules that if a parent
directory has a quota group, any files or directories created in that
parent directory will inherit that quota group, and only processes
with CAP_SYS_ADMIN can change it.
And then what if we simply make the rule that if an inode has a quota
group, the quota is charged against two group id's; the group id named
in inode, and the quota group?
That is, do we really need to have a separate namespace for group ids
and "subtrees" or "namespaces"? That means we don't have to change
the userspace quota tools and we can leverage the existing ways people
are used to managing group quotas.
- Ted
next prev parent reply other threads:[~2012-07-11 13:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 15:28 [PATCH 0/3] RFC: introduce extended inode owner identifier v10 Dmitry Monakhov
2012-07-09 15:28 ` [PATCH 1/3] Add additional owner identifier Dmitry Monakhov
2012-07-09 15:28 ` [PATCH 2/3] ext4: Implement subtree ID support for ext4 filesystem Dmitry Monakhov
2012-07-09 21:04 ` Ted Ts'o
2012-07-11 12:59 ` Dmitry Monakhov
2012-07-11 13:24 ` Theodore Ts'o [this message]
2012-07-11 15:26 ` Dmitry Monakhov
2012-07-11 17:17 ` Ted Ts'o
2012-07-09 15:28 ` [PATCH 3/3] ext4: add subtree quota support Dmitry Monakhov
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=20120711132429.GA10872@thunk.org \
--to=tytso@mit.edu \
--cc=dmonakhov@openvz.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.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).