Hi Dan/Nitin, I've been reading through Seth's patches a bit and looking over the locking in general. I'm wondering why preempt_disable() is used so heavily. Preempt seems to be disabled for virtually all of zcache's operations. It seems a bit unorthodox, and I guess I'm anticipating the future screams of the low-latency folks. :) I think long-term it will hurt zcache's ability to move in to other code. Right now, it's pretty limited to being used in conjunction with memory reclaim called from kswapd. Seems like something we ought to add to the TODO list before it escapes from staging/. -- Dave -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>