Comment 8 for bug 747707

To follow up: Trying 2.6.38-8 (installed the beta and let it update to whatever was current as of 4/9) fixed the problem. kswapd0 no longer hogs CPU, and unlike the OP's report of 4/5, I don't see kworker chewing up time and I see no freezes or other issues. For me, it Just Works. Note that my test was using an "nc | tar" pipeline to push as much stuff to the disk over gigabit as fast as I could, to stress-test things as much as possible. I haven't tried rsync, but see no reason that would act differently. Thanks!