• V
    memcg: do not allow to disable tcp accounting after limit is set · 9ee11ba4
    Vladimir Davydov 提交于
    There are two bits defined for cg_proto->flags - MEMCG_SOCK_ACTIVATED
    and MEMCG_SOCK_ACTIVE - both are set in tcp_update_limit, but the former
    is never cleared while the latter can be cleared by unsetting the limit.
    This allows to disable tcp socket accounting for new sockets after it
    was enabled by writing -1 to memory.kmem.tcp.limit_in_bytes while still
    guaranteeing that memcg_socket_limit_enabled static key will be
    decremented on memcg destruction.
    
    This functionality looks dubious, because it is not clear what a use
    case would be.  By enabling tcp accounting a user accepts the price.  If
    they then find the performance degradation unacceptable, they can always
    restart their workload with tcp accounting disabled.  It does not seem
    there is any need to flip it while the workload is running.
    
    Besides, it contradicts to how kmem accounting API works: writing
    whatever to memory.kmem.limit_in_bytes enables kmem accounting for the
    cgroup in question, after which it cannot be disabled.  Therefore one
    might expect that writing -1 to memory.kmem.tcp.limit_in_bytes just
    enables socket accounting w/o limiting it, which might be useful by
    itself, but it isn't true.
    
    Since this API peculiarity is not documented anywhere, I propose to drop
    it.  This will allow to simplify the code by dropping cg_proto->flags.
    Signed-off-by: NVladimir Davydov <vdavydov@virtuozzo.com>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Michal Hocko <mhocko@kernel.org>
    Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
    Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
    9ee11ba4
memcontrol.c 146.1 KB