2009/8/24 Daniel Lezcano <daniel.lezcano@xxxxxxx> > > > [ snip ] > >> i think that /proc/meminfo should be mounted after /proc . why? i think >>>> that, because mounting /proc may override /proc/meminfo >>>> Am I right? :) >>>> >>>> >>>> >>>> >>> Ha ! haha ! arrgh ! no way ! You are right :/ >>> >>> >>> >> >> Hehe ;) >> >> >> >>> In the case of application container, lxc mounts /proc but in the case of >>> system container it is the system who do that so after the /proc/meminfo >>> has >>> been mounted. >>> >>> Maybe we can look at modifying fs/proc/meminfo.c instead. Let me do a >>> small >>> patch for the kernel... >>> >>> >>> >>> >> Okey. I am waiting for your patch :) >> > > Quick and dirty patch but at least working. It is no synced on the latest > kernel version. > I do not really like to touch fs/proc/meminfo.c but it's an example here. > Hi Daniel, I tried to compile my kernel tree (2.6.30.5) with your patch using gcc-4.4, gcc-4.3 and gcc-4.2 and i got this error on every gcc when linking kernel: mm/built-in.o: In function `mem_cgroup_info': (.text+0x27651): undefined reference to `__udivdi3' mm/built-in.o: In function `mem_cgroup_info': (.text+0x27678): undefined reference to `__udivdi3' mm/built-in.o: In function `mem_cgroup_info': (.text+0x276b0): undefined reference to `__udivdi3' mm/built-in.o: In function `mem_cgroup_info': (.text+0x276dd): undefined reference to `__udivdi3' make: *** [.tmp_vmlinux1] Error 1 this can be gcc based error. What kernel and gcc did you use for compile your kernel? -- Krzysztof Taraszka _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
