Dan, I started writing inline responses to each concern but that was adding more confusion than clarity. I would like to focus the discussion. The purpose of this patchset is to discuss the inclusion of zcache into mainline during the 3.7 merge window. zcache has been a staging since v2.6.39 and has been maturing with contributions from 15 developers (5 with multiple commits) working on improvements and bug fixes. I want good code in the kernel, so if there are particular areas that need attention before it's of acceptable quality for mainline we need that discussion. I am eager to have customers using memory compression with zcache but before that I want to see zcache in mainline. We agree with Konrad that zcache should be promoted before additional features are included. Greg has also expressed that he would like promotion before attempting to add additional features [1]. Including new features now, while in the staging tree, adds to the complexity and difficultly of reverifying zcache and getting it accepted into mainline. [1] https://lkml.org/lkml/2012/3/16/472 Let's have this discussion. If there are specific issues that need to be addressed to get this ready for mainline let's take them one-by-one and line-by-line with patches. Seth -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>