On Wed, Jun 06, 2001 at 12:16:30PM +1000, Andrew Morton wrote: > "Jeffrey W. Baker" wrote: > > > > Because the 2.4 VM is so broken, and > > because my machines are frequently deeply swapped, > > The swapoff algorithms in 2.2 and 2.4 are basically identical. > The problem *appears* worse in 2.4 because it uses lots > more swap. exactly, I've seen this on a 2.2.16 box that went deep into swap. Although it didn't lock up, kswapd was using most of the CPU time during a swapoff. -mh - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Re: Break 2.4 VM in five... Ben Greear
- Re: Break 2.4 VM in five easy ste... Derek Glidden
- Re: Break 2.4 VM in five easy ste... José Luis Domingo López
- Re: Break 2.4 VM in five easy steps Disconnect
- Re: Break 2.4 VM in five easy steps Derek Glidden
- Re: Break 2.4 VM in five easy ste... Helge Hafting
- Re: Break 2.4 VM in five eas... Eric W. Biederman
- Re: Break 2.4 VM in five eas... José Luis Domingo López
- Re: Break 2.4 VM in five easy steps Jeffrey W. Baker
- Re: Break 2.4 VM in five easy steps Eric W. Biederman
- Re: Break 2.4 VM in five easy steps Marc Heckmann
- Re: Break 2.4 VM in five easy steps Hugh Dickins
- Re: Break 2.4 VM in five easy steps Eric W. Biederman
- Re: Break 2.4 VM in five easy steps Jeffrey W. Baker
- Re: Break 2.4 VM in five easy steps Derek Glidden
- Re: Break 2.4 VM in five easy steps Mike A. Harris
- Re: Break 2.4 VM in five easy steps Miles Lane
- Re: Break 2.4 VM in five easy ste... Derek Glidden
- Re: Break 2.4 VM in five eas... Miles Lane
- Re: Break 2.4 VM in five easy ste... Mike A. Harris
- Re: Break 2.4 VM in five easy steps Mike Galbraith