Still not sure what you mean?
My point was that llvmpipe is a pure software renderer, even simple GL stresses the CPU pretty hard - using a compositing manager driven by llvmpipe wouldn't leave much room to do anything else. Power usage is also quite likely to be a major issue compared to doing it on the GPU.
I use kde 4.5. Its compositor do work only with proprietary drivers because it makes use of opengl2 extensions still not supported by open drivers. So I simply do not use it at all and I don't know if it works with LLVMpipe. Anyway kwin 4.4 should run quite well even with llvmpipe.
I tested Extreme Tux Racer and Torcs (same specs as above) and both were nearly playable at 10-15 fps depending on resolution. That's strange, but it seems llvmpipe's speed depends only on resolution, and not on the number of objects/detail/filtering. Anyone can explain this?
We're talking about _llvmpipe_ - a software rasterizer. Think of it as an emulated graphics card, the GPU does not enter in to it.
And I must say, being called a troll when all I do is trying to figure out what your point was... isn't nice.
I don't mind being wrong, there's always an opportunity to learn something new, but I really want to know what it is that I'm wrong about?