The concepts of transcendent memory, including cleancache and frontswap, have now graduated beyond virtualization to have real value in a standalone kernel. See the proposed kztmem patch: http://lwn.net/Articles/423540/ For the page cache, this effectively extends the split LRU (active/inactive) page queues to now include a new "queue" containing compressed clean page cache pages. For swap (as with ramzswap/zram), compressed in-memory swap pages may negatively impact memory pressure in some workloads and a method needs to be contrived to move these pages to a physical swap disk. Some things to discuss: 1) What is the appropriate page count balance between the active queue, the inactive queue, and cleancache-compressed pages? 2) What triggers can be used for rebalancing? 3) Is there a better "source" for cleancache than pages reclaimed from the inactive queue? 4) Under what conditions should frontswap-compressed pages be "repatriated" to normal kernel memory (and possibly to disk)? I also hope to also be able to describe and possibly demo a brand new in-kernel (non-virtualization) user of transcendent memory (including both cleancache and frontswap) that I think attendees in ALL tracks will find intriguing, but I'm not ready to talk about until closer to LSF/MM workshop. (Hopefully, this will make a good lightning talk.) Thanks, Dan Magenheimer -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href