Christoph Lameter <clameter@waterf.org> said:
> I'd really like a stable 2.0.31 as soon as possible.
Yeah I sometimes forget how unstable I'm trying to make 2.0.x,
sheesh...
I too like stability, but too I would like to see that patch in. I haven't
looked at pre-patch-2.0.31 yet, but how about making it a compile time
option, with the default disabled?
If it is shown to create problems it is coming straight out, I believe
it does not do this, so it is staying in until I am convinced
otherwise. There are too many ways in which the changes would need to
be redone (thus undoing all the careful testing that patch was given
in the first place, which is why I let it in) in order to allow it to
be a compile time option.
---------------------------------------------////
Yow! 11.26 MB/s remote host TCP bandwidth & ////
199 usec remote TCP latency over 100Mb/s ////
ethernet. Beat that! ////
-----------------------------------------////__________ o
David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ ><