linux-kernel - Re: [RFC][PATCH] per-uid/gid I/O throttling (was Re: [RFC][PATCH] per-task I/O throttling)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 23 Jan 2008 16:41:18 +0100 (MET)
From:	Andrea Righi <righiandr@...rs.sourceforge.net>
To:	Pavel Machek <pavel@....cz>
Cc:	Balbir Singh <balbir@...ux.vnet.ibm.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Valdis.Kletnieks@...edu, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH] per-uid/gid I/O throttling (was Re: [RFC][PATCH]
 per-task I/O throttling)

Pavel Machek wrote:
> On Tue 2008-01-15 17:49:36, Andrea Righi wrote:
>> 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@...ux:/config/io-throttle# mkdir uid:33
>> root@...ux:/config/io-throttle# cd uid:33/
>> root@...ux:/config/io-throttle/uid:33# cat io-rate
>>      io-rate: 0 KiB/sec
>>    requested: 0 KiB
>> last_request: 0 jiffies
>>        delta: 388202 jiffies
>> root@...ux:/config/io-throttle/uid:33# echo 4096 > io-rate
>> root@...ux:/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:
> 
> Maybe ionice from cfq should be improved, instead?

IMHO it would be interesting to have also a way to use the limiting
approach, instead of i/o priority-based only (i.e. checks to ensure that
servicing the requests will not cause the associated user's maximum
quality of service to be exceeded).

see also http://lkml.org/lkml/2008/1/20/157

-Andrea
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/