public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Glauber Costa <glommer@parallels.com>
To: jeff.liu@oracle.com
Cc: jack@suse.cz, Daniel Lezcano <daniel.lezcano@free.fr>,
	Christopher Jones <christopher.jones@oracle.com>,
	Li Zefan <lizf@cn.fujitsu.com>,
	xfs@oss.sgi.com, Christoph Hellwig <hch@infradead.org>,
	tj@kernel.org, Ben Myers <bpm@sgi.com>,
	tytso@MIT.EDU, lxc-devel@lists.sourceforge.net,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	cgroups@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Re: [RFC PATCH v1 0/4] cgroup quota
Date: Sun, 11 Mar 2012 15:18:36 +0400	[thread overview]
Message-ID: <4F5C8A0C.8050904@parallels.com> (raw)
In-Reply-To: <4F59E78A.7060903@oracle.com>

On 03/09/2012 03:20 PM, Jeff Liu wrote:
> Hello,
>
> Disk quota feature has been asked at LXC list from time to time.
> Given that the project quota has already implemented in XFS for a long time, and it was also in progress for EXT4.
> So the major idea is to assign one or more project IDs(or tree ID?) to container, but leaving quota setup via cgroup
> config files, so all the tasks running at container could have project quota constraints applied.
>
> I'd like to post an initial patch sets here, the stupid implements is very simple and even crash me
> in some cases, sorry! But I would like to submit it to get more feedback to make sure I am going down
> the right road. :)
>
> Let me introduce it now.
>
> 1. Setup project quota on XFS(enabled pquota) firstly.
> For example, the "project100" is configured on "/xfs/quota_test" directory.
>
> $ cat /etc/projects
> 100:/xfs/quota_test
>
> $ cat /etc/projid
> project100:100
>
> $ sudo xfs_quota -x -c 'report -p'
> Project quota on /xfs (/dev/sda7)
>                                 Blocks
> Project ID       Used       Soft       Hard    Warn/Grace
> ---------- --------------------------------------------------
> project100          0          0          0     00 [--------]
>
> 2. Mount cgroup on /cgroup.
> cgroup on /cgroup type cgroup (rw)
>
> After that, there will have a couple of quota.XXXX files presented at /cgroup.
> $ ls -l /cgroup/quota.*
> --w------- 1 root root 0 Mar  9 18:27 /cgroup/quota.activate
> --w------- 1 root root 0 Mar  9 18:27 /cgroup/quota.add_project
> -r--r--r-- 1 root root 0 Mar  9 18:27 /cgroup/quota.all
> --w------- 1 root root 0 Mar  9 18:27 /cgroup/quota.block_limit_in_bytes
> --w------- 1 root root 0 Mar  9 18:27 /cgroup/quota.deactivate
> --w------- 1 root root 0 Mar  9 18:27 /cgroup/quota.inode_limit
> -r--r--r-- 1 root root 0 Mar  9 18:27 /cgroup/quota.projects
> --w------- 1 root root 0 Mar  9 18:27 /cgroup/quota.remove_project
> --w------- 1 root root 0 Mar  9 18:27 /cgroup/quota.reset_block_limit_in_bytes
> --w------- 1 root root 0 Mar  9 18:27 /cgroup/quota.reset_inode_limit
>
> 3. To assign a project ID to container, just echo it to quota.add_project as:
> echo "project100:100">  /cgroup/quota.add_project
>
> To get a short list of the current projects assigned to container, user can check quota.projects,
> # cat /cgroup/quota.projects
> Project ID (project100:100)	status: off
>
> The totally quota info can be check against quota.all, it will show something like below:
> # cat /cgroup/quota.all
> Project ID (project100:100)	status: off
>    block_soft_limit	9223372036854775807
>    block_hard_limit	9223372036854775807
>    block_max_usage	0
>    block_usage	0
>    inode_soft_limit	9223372036854775807
>    inode_hard_limit	9223372036854775807
>    inode_max_usage	0
>    inode_usage	0
>
> Note that about "status: off", by default, a new assigned project will in OFF state, user could
> turn it on by echo the project ID to quota.activate as below:
> # echo 100>  /cgroup/quota.activate
> # cat /cgroup/quota.all
> Project ID (project100:100)	status: on	 *now  status changed.*
>    block_soft_limit	9223372036854775807
>    block_hard_limit	9223372036854775807
>    block_max_usage	0
>    block_usage	0
>    inode_soft_limit	9223372036854775807
>    inode_hard_limit	9223372036854775807
>    inode_max_usage	0
>    inode_usage	0
>
> But it will do nothing since without quota setup.
>
> 4. To configure quota via cgroup, user need to interact with quota.inode_limit and quota.block_limit_in_bytes.
> For now, I only add a simple inode quota check to XFS, it looks something like below:
>
> # echo "100 2:4">>  /cgroup/quota.inode_limit
> # cat /cgroup/quota.all
> Project ID (project100:100)	status: on
>    block_soft_limit	9223372036854775807
>    block_hard_limit	9223372036854775807
>    block_max_usage	0
>    block_usage	0
>    inode_soft_limit	2
>    inode_hard_limit	4
>    inode_max_usage	0
>    inode_usage	0
>
> # for ((i=0; i<  6; i++)); do touch xfs/quota_test/test.$i; done
>
> Project ID (project100:100)	status: on
>    block_soft_limit	9223372036854775807
>    block_hard_limit	9223372036854775807
>    block_max_usage	0
>    block_usage	0
>    inode_soft_limit	2
>    inode_hard_limit	4
>    inode_max_usage	4
>    inode_usage	4
>
> Sorry again, above steps crashed me sometimes for now, it works just for demo purpose. :)
>
> Any criticism and suggestions are welcome!

I have mixed feelings about this. The feature is obviously welcome, but 
I am not sure if
the approach you took is the best one... I'll go through the patches 
now, and hopefully will
have a better opinion by the end =)

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

  reply	other threads:[~2012-03-11 11:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 11:20 [RFC PATCH v1 0/4] cgroup quota Jeff Liu
2012-03-11 11:18 ` Glauber Costa [this message]
2012-03-11 10:50   ` Jeff Liu
2012-03-11 11:57 ` Glauber Costa
2012-03-11 11:47   ` Jeff Liu
2012-03-12  9:36     ` Glauber Costa
2012-03-12  7:11       ` Jeff Liu

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=4F5C8A0C.8050904@parallels.com \
    --to=glommer@parallels.com \
    --cc=bpm@sgi.com \
    --cc=cgroups@vger.kernel.org \
    --cc=chris.mason@oracle.com \
    --cc=christopher.jones@oracle.com \
    --cc=daniel.lezcano@free.fr \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=jeff.liu@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=lxc-devel@lists.sourceforge.net \
    --cc=tj@kernel.org \
    --cc=tytso@MIT.EDU \
    --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