linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Dave Chinner <david@fromorbit.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: Sat, 9 Aug 2014 20:09:51 -0400	[thread overview]
Message-ID: <20140810000951.GI15431@thunk.org> (raw)
In-Reply-To: <20140809233832.GM20518@dastard>

On Sun, Aug 10, 2014 at 09:38:32AM +1000, Dave Chinner wrote:
> 
> I've seen this sort of thing quite a bit over the past 10 years.
> Most of the time on storage systems measured in the high tens to
> hundreds of TB of storage, which puts it way out of the scope of
> knowledge of most Linux distro and application developers. That's
> most likely why you don't get any other answer to your questions -
> most people can't see how project quotas get used because they've
> never worked in a large, multi-project environment before.

Sure, but the people who are advocating for project quotas had better
understand how they plan to use them, both so that (a) if they do a
design different from XFS, they can justify why the differences are
necessary, and (b) to justify whether we need it in ext4 to begin
with.

The "directory hierarchy quota" is easy to understand, it's something
that the Andrew File System had --- down to restriction that you can't
move a file between different AFS volumes, but instead have to copy
and unlink.

> If we need a more *complex* solution because people need more than
> just what the simple solution gives them, then that is a topic for
> -fsdevel and probably LSFMM because there's all sorts of semantic
> and interface discussions that are needed and a lot more code that
> needs to be written. i.e. the simple solution can be deployed within
> a couple of kernel releases, a generic solution is more likely a
> coupleof *years* of work to deploy...

100% agreed.  And I have yet to see a compelling case that even the
simple form of project id's would get a lot of use in the ext4 world.
Which is why I want to know from those who want to add project quotas
in to ext4.  How do you plan to use them?  What's the use case
scenario?

							- Ted

  reply	other threads:[~2014-08-10  0:12 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 [this message]
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
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=20140810000951.GI15431@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger@dilger.ca \
    --cc=david@fromorbit.com \
    --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).