On 10/26/2012 12:37 AM, Dhaval Giani wrote: > 1. When do you know the memory limit? Is it something that is figured > out at runtime, or you can put it in some file which can then loaded > in by cgrules? I don't think either of the methods are harder than the > other, but it really is a question of knowing what interface to > provide.
In my precise case, I know the limit before launching the program (I don't want to allow any program to use more than 90% - for example - of the physical memory). In the end, I just want to have a working limits.conf rss :D > Now, I am sure > we can have a solution for you, but I am also sure that I will find at > least 10 persons coming and telling me that that policy is broken ;-). I understand perfectly your concerns about the big picture. I just came here as a typical end user "I want to do that, this looks very simple to me (limit physical memory usage of every program), please help me" ;) > So, I am very happy to accept patches (at least to create cgroups > dynamically), however I would like some sane policy mechanism, and if > you figure it out, you are my hero :D. I think that Roberto Polli (see the thread "[patching...] trying to add per-process limits on memory subsystem." from yesterday) is already working in the right direction (from my user point of view of course). Concerning the policy mechanism, I'm just in the beginning to understand the whoel cgroup philosophy, so I don't think you will get any help from me, at least at the moment. Thank you for your answer ! Jean-Baptiste ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Libcg-devel mailing list Libcg-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libcg-devel
