That does make a difference. kswapd does its clean-up in a loop that runs
with very high priority every time it thinks that there are not enough free
pages. The process will only run this code if it actually fails to find a
free page, and if I understand correctly, do so with its regular priority,
right?
In my case, I do not mind if the process gets stuck looking for a free page
while letting other processes that already have all the pages they need run,
as opposed to kswapd monopolizing the CPU trying to clean up.
So, I would like to reiterate that kswapd disabling feature would be very
helpful to have in the kernel. It involves only trivial code changes, and it
does allow a sysadmin to do things a different way - like I said earlier,
Linux is about choice, and when it is possible, one should have it.
But actually, digging a little deeper - I think there is still a bug in
shrink_caches(). Even after disabling kswapd, in one instance I had a process
brutally murdered at the time when I had over 100MB of cache available. The
cache was heavily used and growing, if that helps any.
It must be noted that the one process murder in this case did not compare
with a massacre that happened in the same situation when kswapd was not
disabled. About 10 processes got killed.
-- MySQL Development Team For technical support contracts, visit https://order.mysql.com/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Sasha Pachev <sasha@mysql.com> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Provo, Utah, USA <___/ - 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/