Date: Sat, 7 Aug 2010 13:10:45 GMT From: Edward Tomasz Napierala <trasz@FreeBSD.org> To: Perforce Change Reviews <perforce@freebsd.org> Subject: PERFORCE change 182023 for review Message-ID: <201008071310.o77DAjKR094723@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://p4web.freebsd.org/@@182023?ac=10 Change 182023 by trasz@trasz_victim on 2010/08/07 13:09:45 Update TODO. Affected files ... .. //depot/projects/soc2009/trasz_limits/TODO#22 edit Differences ... ==== //depot/projects/soc2009/trasz_limits/TODO#22 (text+ko) ==== @@ -39,6 +39,29 @@ Issues: + - In the long term, the goal is to get rid of lim_get(9), chgproccnt(9) etc, + turning this: + + limit = lim_get(...); + if (value > limit) + return (EWHATEVER); + + [ do stuff ] + + into this: + + if (rusage_add(...)) + return (EWHATEVER); + + [ do stuff ] + + if (some error) + rusage_sub(...); + + However, this requires per-process limit enforcement to be hooked into + container mechanism. This is a part of HRL, and it's outside the scope + of the containers project. This means the code is full of "#ifdef CONTAINERS". + - Don't account resources for system processes. It's not as easy as checking for P_SYSTEM flag, as the flag will be set for AIO kernel processes.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201008071310.o77DAjKR094723>