Another way to solve this is to switch the user context right? Isnt it possible to avoid these patches if do the allocation in another task context instead? Are there really any other use cases beyond fsnotify? The charging of the memory works on a per page level but the allocation occur from the same page for multiple tasks that may be running on a system. So how relevant is this for other small objects? Seems that if you do a large amount of allocations for the same purpose your chance of accounting it to the right memcg increases. But this is a game of chance. -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
