linuxaudio.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)

--------------enig490FA011ECBB9820203C858B

Content-Type: text/plain; charset=ISO-8859-1

Content-Transfer-Encoding: quoted-printable
On 02/23/2011 11:10 AM, Olivier Guilyardi wrote:
> The dynamic cgroups solution seems good.

quoted text
>=20

> On Android there basically is one priviledged and trusted audio process=

,

quoted text
> audioflinger, the sound server, which performs mixing and access the ha=

rdware.

quoted text
> All audio clients are untrusted. I think there is a need to both assign=

 a

quoted text
> careful cpu.rt_runtime_us to each client but also to limit the number o=

f clients

quoted text
> which can run at the same time. This would allow to keep the CPU time a=

ssigned

quoted text
> to all clients within a certain quota, but also to prevent clients from=

 fighting

quoted text
> with each other for realtime bandwidth.

>=20

> Can you limit the maximum number of realtime processes with ulatencyd?

Yes, that should be possible, even i never used that. So, you want a

first come first get policy ?
There is no nice api for detecting the number of processes in a group

but i will add one as i think it's a valid decision to consider. There

is no per se limit of processes in a group, in fact: there is no way to

limit processes numbers anyhow, unfortunately. Makes it very hard to

write write a fork bomb protector ;-)
But, you can of course just stop moving processes into a group.
Yesterday i added a instant filter functionality that allows you with

witelists to move processes extremly quickly. This is required for some

daemons that request realtime and then messure the cpu time they get to

test if it's enough for running smoothly. Those problematic processes

must be whitelisted because the normal delay mechanism would schedule

them to late, as many processes started are just short running and

looking at them is just a waste of cpu time.
kind regards

 Daniel
--------------enig490FA011ECBB9820203C858B

Content-Type: application/pgp-signature; name="signature.asc"

Content-Description: OpenPGP digital signature

Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----

Version: GnuPG v1.4.10 (GNU/Linux)

Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJNZULKAAoJEFYpgV2RoepcAsYQAMSb9G6CzDTkGjZC901uQ9Ak

74kBfysmgCE9MkTnzSw5g0fBgvlHAhDnExBCWUCNnMBrjz1jaZMrRap++wi30AFi

rcG+Ty0THfnFHt3fKZCzAVvem3I5v+kLymuodQtwzqWGz+YYbmzLNy/r6UXkIQha

Ngfk96QIuwqF9lFDMUbGM3y09koSqoLiqRIjMeUnbe9uKuRVeT1fkAnWJqoz4YTH

H1zslNbq6A9lQfJe9QlGVRaEnxo8LUlUIWZckfvEskxsUxtDOJxqY7QwenEBuNGG

4imKK1fVclmwVWbVk+42VN1LAdBxGDuCIhiliZuzio8zdL5FeFBbIRndPnMH65yA

qK9Ub151vgEEpPjItLZbDgdeFbDa1khb1b/foN5azr4hzj69RSozFqKaOS955yjE

INLBTCYI+f9znxAQ+4Iu2Tsnrv+axabtauIW6bPDY/gBOdqoOzsv5CGhvtyonZCf

ErnH0o39HL7u+ikunOKV10qcNB2iQr7mGfoK7K4LrAgqyEDwximX+r3I6SiP+n/M

TLKgdw9oxErVsQb0EqHvDuFi3dnusYzQSkn9COKLk4Q7C/AmQLuI12LXdrkM0CYr

v1Q1S8USIBHtW7prydkkKF5XWFBk/BamC/5yY9UrPDaLb0jrZNLbnuWfosxzQjYk

TE5UM0f+9ZwSffJLK9YP

=MfJ9

-----END PGP SIGNATURE-----
--------------enig490FA011ECBB9820203C858B--