Hi,
When using ramzswap, the internal allocator (xvMalloc) will try to
grow the pool,
when the compressed block will not fit in any of the existing free chunk.
This memory allocation can fail under low memory.
This will be informed to the kernel as a "device write" failure. The
page which was being written will
not be reclaimed, but the kernel will continue to try swap out of
other pages ( as kernel
thinks that swap has free space. )
Wont this lead to the reclaim code ( kswapd or the direct reclaim
path ) hogging the processor for some time
before OOM is finally announced ?
Has any one analysed this scenario ?
thanks
shankar
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxxx For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>