Re: [PATCH v2] fs: fsnotify: account fsnotify metadata to kmemcg
From: Shakeel Butt <hidden>
Date: 2018-01-25 20:20:05
Also in:
linux-fsdevel, lkml
From: Shakeel Butt <hidden>
Date: 2018-01-25 20:20:05
Also in:
linux-fsdevel, lkml
On Wed, Jan 24, 2018 at 11:51 PM, Amir Goldstein [off-list ref] wrote:
There is a nicer alternative, instead of failing the file access, an overflow event can be queued. I sent a patch for that and Jan agreed to the concept, but thought we should let user opt-in for this change: https://marc.info/?l=linux-fsdevel&m=150944704716447&w=2 So IMO, if user opts-in for OVERFLOW instead of ENOMEM, charging the listener memcg would be non controversial. Otherwise, I cannot say that starting to charge the listener memgc for events won't break any application.
Thanks Amir, I will send out patches soon for directed charging for fsnotify. Also are you planning to work on the opt-in overflow for the above case? Should I wait for your patch? thanks, Shakeel -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>