From: Theodore Ts'o <tytso@mit.edu>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Li Xi <pkuelelixi@gmail.com>,
linux-fsdevel@vger.kernel.org,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
viro@zeniv.linux.org.uk, hch@infradead.org,
Jan Kara <jack@suse.cz>, Andreas Dilger <adilger@dilger.ca>,
"Niu, Yawei" <yawei.niu@intel.com>
Subject: Re: [PATCH v2 0/4] quota: add project quota support
Date: Sun, 10 Aug 2014 17:49:43 -0400 [thread overview]
Message-ID: <20140810214943.GL15431@thunk.org> (raw)
In-Reply-To: <1407703644.8477.1.camel@jarvis.lan>
On Sun, Aug 10, 2014 at 01:47:24PM -0700, James Bottomley wrote:
>
> Actually, I don't believe that's entirely accurate. The performance
> problem with shared filesystem roots for containers has meant OpenVZ has
> been using a block root for a while. However, we still support the old
> shared filesystem root, but for quota's within the chroot, we use a subtree
> quota system (not a project quota) for which Dmitry Monakhov
> posted the patches several times a couple of years ago.
The XFS-compatible project quota is effectively a subtree quota
system. My argument is that if we're going to try to get something
like this upstream, it should have the same properties as the XFS
project quota system; and that should be semantically compatible with
the patches you are using.
(If we end up using the same ioctl's as xfs_quota uses, which in
theory I'm in favor of, but which I haven't studied yet, then it might
not be ABI compatible with Dmitry's patches, but it should simplify
the patches that OpenVZ would need to carry.)
- Ted
next prev parent reply other threads:[~2014-08-10 21:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 16:39 [PATCH v2 0/4] quota: add project quota support Li Xi
2014-08-08 22:33 ` Theodore Ts'o
2014-08-09 14:24 ` Li Xi
2014-08-09 17:24 ` Theodore Ts'o
2014-08-09 22:17 ` Theodore Ts'o
2014-08-09 23:38 ` Dave Chinner
2014-08-10 0:09 ` Theodore Ts'o
2014-08-10 22:18 ` Dave Chinner
2014-08-10 2:15 ` Li Xi
2014-08-11 10:49 ` Jan Kara
2014-08-10 8:38 ` Shuichi Ihara
2014-08-10 16:52 ` Theodore Ts'o
2014-08-10 20:47 ` James Bottomley
2014-08-10 21:49 ` Theodore Ts'o [this message]
2014-08-09 22:14 ` Dave Chinner
2014-08-11 14:41 ` Theodore Ts'o
2014-08-12 15:35 ` Dmitry Monakhov
-- strict thread matches above, loose matches on Subject: below --
2014-08-08 16:58 Li Xi
2014-08-10 0:38 Li Xi
2014-08-11 0:06 Li Xi
2014-08-11 0:19 Li Xi
2014-08-11 10:23 Li Xi
2014-08-11 13:48 ` Theodore Ts'o
2014-08-11 14:16 Li Xi
2014-08-11 14:40 Li Xi
2014-08-11 14:45 ` Theodore Ts'o
2014-08-11 14:49 ` Li Xi
2014-08-11 15:03 Li Xi
2014-08-13 2:32 Li Xi
2014-08-13 13:22 ` Theodore Ts'o
2014-08-14 1:34 Li Xi
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=20140810214943.GL15431@thunk.org \
--to=tytso@mit.edu \
--cc=James.Bottomley@hansenpartnership.com \
--cc=adilger@dilger.ca \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pkuelelixi@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yawei.niu@intel.com \
/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).