On Sat, 2012-07-07 at 14:26 -0400, Rik van Riel wrote: > > You asked how and why Andrea's algorithm converges. > After looking at both patch sets for a while, and asking > for clarification, I think I can see how his code converges. Do share.. what does it balance on and where does it converge to? > It is not yet clear to me how and why your code converges. I don't think it does.. but since the scheduler interaction is fairly weak it doesn't matter too much from that pov. > I see some dual bin packing (CPU & memory) heuristics, but > it is not at all clear to me how they interact, especially > when workloads are going active and idle on a regular basis. > Right, this is the bit I wanted discussion on most.. it is not at all clear to me what one would want it to do. Given sufficient memory you'd want it to slowly follow the cpu load. However on memory pressure you can't do that. Spreading memory evenly across nodes doesn't make much sense if the compute time and capacity isn't matched either. Also a pond will never settle if you keep throwing rocks in, you need semi-stable operation conditions for anything to make sense. So the only thing to consider for the wildly dynamic case is not going bananas along with it. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href