linux-kernel - Re: i/o bandwidth controller infrastructure

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-next>] [day] [month] [year] [list]

Date:	Mon, 16 Jun 2008 13:51:34 -0700
From:	Divyesh Shah <dpshah@...gle.com>
To:	Andrea Righi <righi.andrea@...il.com>, balbir@...ux.vnet.ibm.com,
	menage@...gle.com
Cc:	linux-kernel@...r.kernel.org, axboe@...nel.dk, matt@...ehost.com,
	roberto@...it.it, randy.dunlap@...cle.com,
	akpm@...ux-foundation.org
Subject: Re: i/o bandwidth controller infrastructure

>
> This is the core io-throttle kernel infrastructure. It creates the
> basic
> interfaces to cgroups and implements the I/O measurement and
> throttling
> functions.

I am not sure if throttling an application's cpu usage by explicitly  
putting it to sleep
in order to restrain it from making more IO requests is the way to go  
here (though I can't think
of anything better right now).
With this bandwidth controller, a cpu-intensive job which otherwise  
does not care about its IO
performance needs to be pin-point accurate about IO bandwidth  
required in order to not suffer
from cpu-throttling. IMHO, if a cgroup is exceeding its limit for a  
given resource, the throttling
should be done _only_ for that resource.

-Divyesh
--
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/