linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Christoph Hellwig <hch@infradead.org>,
	Ilya Pronin <ipronin@twitter.com>,
	linux-xfs@vger.kernel.org
Subject: Re: Reading/changing projid of a symlink
Date: Fri, 15 Jun 2018 02:00:23 -0700	[thread overview]
Message-ID: <20180615090023.GA7411@infradead.org> (raw)
In-Reply-To: <20180615085724.pkpfpmuas5ujmcbw@odin.usersys.redhat.com>

On Fri, Jun 15, 2018 at 10:57:24AM +0200, Carlos Maiolino wrote:
> Thanks for the info. I always thought project quotas were designed for
> directory-tree granularity, and user/group quotas as a file-based granularity.
> But, out of curiosity, if this is not a stupid question...
> If project quotas was initially designed as a per-file usage use case in mind,
> what would make it different from group quota for example?

IRIX had projects integrated into the whole OS, that these did fit into.
Group quotas were only added to XFS after the Linux port.

  reply	other threads:[~2018-06-15  9:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31  0:26 Reading/changing projid of a symlink Ilya Pronin
2018-06-12 14:36 ` Carlos Maiolino
2018-06-12 22:17   ` Ilya Pronin
2018-06-13  6:23     ` Christoph Hellwig
2018-06-13 14:22       ` Eric Sandeen
2018-06-13  9:40     ` Carlos Maiolino
2018-06-15  0:14       ` Ilya Pronin
2018-06-15  7:08         ` Carlos Maiolino
2018-06-15  7:12           ` Christoph Hellwig
2018-06-15  8:57             ` Carlos Maiolino
2018-06-15  9:00               ` Christoph Hellwig [this message]
2018-06-14  2:31     ` Dave Chinner

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=20180615090023.GA7411@infradead.org \
    --to=hch@infradead.org \
    --cc=ipronin@twitter.com \
    --cc=linux-xfs@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).