On 10/4/07, Balbir Singh <balbir@xxxxxxxxxxxxxxxxxx> wrote: > > Forbidding writing to the root resource counter is a policy decision > I am unable to make up my mind about. It sounds right, but unless > we have a notion of unlimited resources, I am a bit concerned about > taking away this flexibility. One big reason for doing this is to make virtualization easier - if you expect not to be able to write to your root cgroup's limits files, then it's easier to make them non-writeable for a virtual server. > > >> One arguable drawback to this patch is that the use of memparse() is > >> lost in the cleanup. Having said that, given the existing of shell > >> arithmetic, it's not clear to me that typing > >> > > memparse(), makes it so much easier, we need to use it. > > >> echo $[2<<30] > memory.limit > >> > > Very geeky! I don't like it personally Why do you dislike it? Do you really believe that anyone using this interface by hand isn't going to know that MB is 2^20 and GB is 2^30? > > Do read_uint() and write_uint(), just read and write unsigned > integers? Correct. Paul _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
