On Thu, 13 Oct 2022 00:54:31 +0000 Shakeel Butt wrote: > So, before the patch, the memcg code may force charges but it will > return false and make the networking code to uncharge memcg for > SK_MEM_RECV. Ah, right, I see it now :( I guess I'll have to try to test (some approximation of) a revert after all. Did the fact that we used to force charge not potentially cause reclaim, tho? Letting TCP accept the next packet even if it had to drop the current one?
