> -----Original Message----- > From: ext KOSAKI Motohiro [mailto:kosaki.motohiro@xxxxxxxxx] > Sent: 08 June, 2012 10:23 ... > > If you wakeup only by signal when memory situation changed you can be > not mlocked. > > Mlocking uses memory very inefficient way and usually cannot be applied > for apps which wants to be notified due to resources restrictions. > > That's your choice. If you don't need to care cache dropping, We don't > enforce it. I only pointed out your explanation was technically incorrect. My explanation is correct. That is an overhead you have to pay if start to use API based on polling from user-space and this overhead narrows API applicability. Moving all times/tracking to kernel avoid useless wakeups in user-space. -- 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