public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Liu <jeff.liu@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: Question about project quota with container
Date: Wed, 29 Feb 2012 15:21:39 +0800	[thread overview]
Message-ID: <4F4DD203.5090705@oracle.com> (raw)
In-Reply-To: <20120229083633.GA14241@infradead.org>

Hi Christoph,

Thanks for you prompt response!

On 02/29/2012 04:36 PM, Christoph Hellwig wrote:

>> I was wondering if other file system will also implement project quota
>> based on these two configuration files in the future? In other words, is
>> it a standard?
> 
> The have been a few attempts at roughly similar quotas for ext4, but
> they were incompatible enough to not reuse any infrastructure like this.

> 
>>
>> Alternatively, maybe the project path and ID can be setup at cgroup
>> control files too, the following things could be implemented like
>> "xfsprogs/quota/edit.c", but I would put aside this idea for now.
> 
> Assigning the project IDs in the cgroups code sounds fine to me.

Ok, I'll try it first.

> To make peoples life's easier it might be good idea to keep the
> /etc/projects and /etc/projid files uptodate even from that code.

To update these two files at cgroup is also fine to me.

Thanks,
-Jeff

> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2012-02-29 10:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29  1:49 Question about project quota with container Jeff Liu
2012-02-29  8:36 ` Christoph Hellwig
2012-02-29  7:21   ` Jeff Liu [this message]

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=4F4DD203.5090705@oracle.com \
    --to=jeff.liu@oracle.com \
    --cc=hch@infradead.org \
    --cc=xfs@oss.sgi.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