>> People tried to do this before, but got rejected by upstream maintainers, >> and then the opinion was to do this in userspace throught FUSE. >> >> Seems libvirt-lxc already supports containerized /proc/meminfo in this way. >> See: >> http://libvirt.org/drvlxc.html > > I'm well aware of the FUSE approach and the fact that the kernel maintainers do not accept the this kind of changing the kernel but the simple truth is that FUSE is too have for this thing. > > I'm setting up a repo on GitHub which will hold all the patches for this and will keep updating it even if it is not accepted by the upstream maintainers. I'll give you the link within a few days. > > I have already finished with CPU and Memory... the only thing that is left is the /proc/loadavg, which will take more time, but will be done. > > I hope some of the scheduler maintainers at least to give me some comments on the patches that I have done. > Then you should add Peter, Ingo and LKML to your Cc list. :) -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
