> After 11 days of uptime your patch is working GREAT. Although cache is
> filled up again and there is only 70 megs free of memory top is
> reporting. I assume that this is just normal behavior. When rsync runs,
> memory from buff is free allowing rsync the memory to run seamless.
Yes, the cache is allowed to take all memory in the system, but
when something needs to run the memory will be reclaimed.
Of course it's also possible that program memory will be swapped
out instead of reclaiming from the cache, but the way rmap is
balanced means that the system is more likely to swap out cache
memory .. unless the memory from the cache is heavily accessed.
> And I notice that the kswapd time that top is reporting is far less than
> say the 2.4.18 kernel vanilla or 2.4.8 vanilla (two other boxes with the
> same configurations). Why is this?
Kswapd removes the right pages from RAM, that is: pages that will
not be used again soon (most likely). This also means it doesn't
need to read those pages in again from disk and the VM is less
busy as a result.
It also changes some data structures inside the kernel to remove
some of the complexity in chosing which page to evict from RAM,
meaning that it can choose the right page to evict with less CPU
usage.
kind regards,
Rik
-- Bravely reimplemented by the knights who say "NIH".http://www.surriel.com/ http://distro.conectiva.com/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/