Greetings from SCALE7x! Today will be the second (and the last) day of the show. Yesterday I did a presentation titled "Recent Advances in the Linux Kernel resource management". The scope of the talk is much more technical and narrow than my usual talk about containers. More to say, I was focusing more on mainstream Linux kernel (i.e. cgroups and memory controller) than on OpenVZ kernel (i.e. user beancounters).
I think the talk was well received and I had about 10 different interesting questions, one is puzzling enough so I was not able to provide a good answer. This is definitely a sign of a good audience.
If anyone is interested in slides from my presentation, they are available: OpenOffice ODP (276K), PDF (409K), PPT (437K).
I think the talk was well received and I had about 10 different interesting questions, one is puzzling enough so I was not able to provide a good answer. This is definitely a sign of a good audience.
If anyone is interested in slides from my presentation, they are available: OpenOffice ODP (276K), PDF (409K), PPT (437K).


Comments
Now, we have settled on 2.6.27 for quite a while because it's stated to be a long maintained kernel; updates for this kernel are still coming (and I hope will come for some time). That makes it a good platform for OpenVZ. Our current goal is to eventually stop maintaining 2.6.24 and 2.6.26 kernels and only leave 2.6.18-rhel5 (stable) and 2.6.27 (devel).
Currently we have no plans for 2.6.28 and 2.6.29, but this might change :)
thanks for the explanation.
Having 2.6.27 as a base for OpenVZ is absolutely fine with me, considering that 2.6.27 is the basis for openSUSE 11.1 and SLES 11.
Merging OpenVZ functionality to mainstream is indeed preferable to porting the patchset.