Hi, Team I've been wondering if we should publish a roadmap. There are several items on my wish list, I thought I'll share them for comments and thoughts
a. libcg needs a layer 2 API For e.g., setting cpu shares should be supported via a CPU shares API. libcg_set_cpu_shares() Setting memory cgroup limits should be supported as libcg_set_memcg_hard_limit b. When I designed the first iteration of libcg, I made it like udev with a client<->server architecture. For simplicity then we moved to the client only model. I propose we support the client only model plus consider adding a server side component. The idea being a. If limits change or a client changes something, there is no way to do notification today, we need to walk the entire tree b. We need a consistent view of the filesystem so that we can make global changes Comments? Balbir Singh. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ Libcg-devel mailing list Libcg-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libcg-devel
