From: Andrea Righi <righiandr@users.sourceforge.net>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Valdis.Kletnieks@vt.edu, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] per-uid/gid I/O throttling (was Re: [RFC][PATCH] per-task I/O throttling)
Date: Wed, 16 Jan 2008 13:58:11 +0100 (MET) [thread overview]
Message-ID: <478DFF62.3070408@users.sourceforge.net> (raw)
In-Reply-To: <20080116104541.GB25724@balbir.in.ibm.com>
Balbir Singh wrote:
> * Andrea Righi <righiandr@users.sourceforge.net> [2008-01-15 17:49:36]:
>
>> Allow to limit the I/O bandwidth for specific uid(s) or gid(s) imposing
>> additional delays on those processes that exceed the limits defined in a
>> configfs tree.
>>
>> Examples:
>>
>> Limit the I/O bandwidth for user www-data (UID 33) to 4MB/s:
>>
>> root@linux:/config/io-throttle# mkdir uid:33
>> root@linux:/config/io-throttle# cd uid:33/
>> root@linux:/config/io-throttle/uid:33# cat io-rate
>> io-rate: 0 KiB/sec
>> requested: 0 KiB
>> last_request: 0 jiffies
>> delta: 388202 jiffies
>> root@linux:/config/io-throttle/uid:33# echo 4096 > io-rate
>> root@linux:/config/io-throttle/uid:33# cat io-rate
>> io-rate: 4096 KiB/sec
>> requested: 0 KiB
>> last_request: 389271 jiffies
>> delta: 91 jiffies
>>
>> Limit the I/O bandwidth of group backup (GID 34) to 512KB/s:
>>
>> root@linux:/config/io-throttle# mkdir gid:34
>> root@linux:/config/io-throttle# cd gid:34/
>> root@linux:/config/io-throttle/gid:34# cat io-rate
>> io-rate: 0 KiB/sec
>> requested: 0 KiB
>> last_request: 0 jiffies
>> delta: 403160 jiffies
>> root@linux:/config/io-throttle/gid:34# echo 512 > io-rate
>> root@linux:/config/io-throttle/gid:34# cat io-rate
>> io-rate: 512 KiB/sec
>> requested: 0 KiB
>> last_request: 403618 jiffies
>> delta: 80 jiffies
>>
>> Remove the I/O limit for user www-data:
>>
>> root@linux:/config/io-throttle# echo 0 > uid:33/io-rate
>> root@linux:/config/io-throttle# cat uid:33/io-rate
>> io-rate: 0 KiB/sec
>> requested: 0 KiB
>> last_request: 419009 jiffies
>> delta: 568 jiffies
>>
>> or:
>>
>> root@linux:/config/io-throttle# rmdir uid:33
>>
>> Future improvements:
>> * allow to limit also I/O operations per second (instead of KB/s only)
>> * extend grouping criteria (allow to define rules based on process containers,
>> process command, etc.)
>>
>> Signed-off-by: Andrea Righi <a.righi@cineca.it>
>
> Hi, Andrea,
>
> Thanks for doing this. I am going to review the patches in greater
> detail and also test them. Why do you use configfs when we have a
> control group filesystem available for grouping tasks and providing a
> file system based interface for control and accounting?
>
Well... I didn't choose configfs for a technical reason, but simply
because I'm more familiar with it, respect to the other equivalent ways
to implement this. But I'll try to look also at the control group
approach, I don't know in details all the advantages/disadvantages, but
it seems interesting anyway.
-Andrea
prev parent reply other threads:[~2008-01-16 12:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 22:45 [RFC][PATCH] per-task I/O throttling Andrea Righi
2008-01-11 1:50 ` Bill Davidsen
2008-01-11 10:28 ` Andrea Righi
2008-01-11 14:20 ` Peter Zijlstra
2008-01-11 15:29 ` Andrea Righi
2008-01-11 14:05 ` David Newall
2008-01-11 15:44 ` Andrea Righi
2008-01-16 19:21 ` David Newall
2008-01-11 15:59 ` Balbir Singh
2008-01-11 16:32 ` Andrea Righi
2008-01-12 4:57 ` Valdis.Kletnieks
2008-01-12 9:46 ` Peter Zijlstra
2008-01-12 10:57 ` Balbir Singh
2008-01-12 11:10 ` Peter Zijlstra
2008-01-12 18:01 ` Andrea Righi
2008-01-13 4:46 ` Balbir Singh
2008-01-15 16:49 ` [RFC][PATCH] per-uid/gid I/O throttling (was Re: [RFC][PATCH] per-task I/O throttling) Andrea Righi
2008-01-11 17:58 ` Pavel Machek
2008-01-23 15:41 ` Andrea Righi
2008-01-16 10:45 ` Balbir Singh
2008-01-16 11:30 ` Valdis.Kletnieks
2008-01-16 12:05 ` Balbir Singh
2008-01-16 12:24 ` Valdis.Kletnieks
2008-01-16 12:58 ` Andrea Righi [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=478DFF62.3070408@users.sourceforge.net \
--to=righiandr@users.sourceforge.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=a.p.zijlstra@chello.nl \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@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