From: Johannes Weiner <hannes@cmpxchg.org>
To: Roman Gushchin <guro@fb.com>
Cc: linux-mm@kvack.org, Michal Hocko <mhocko@kernel.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
cgroups@vger.kernel.org, kernel-team@fb.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: memcontrol: use per-cpu stocks for socket memory uncharging
Date: Tue, 29 Aug 2017 15:26:21 -0400 [thread overview]
Message-ID: <20170829192621.GA5447@cmpxchg.org> (raw)
In-Reply-To: <20170829100150.4580-1-guro@fb.com>
On Tue, Aug 29, 2017 at 11:01:50AM +0100, Roman Gushchin wrote:
> We've noticed a quite sensible performance overhead on some hosts
> with significant network traffic when socket memory accounting
> is enabled.
>
> Perf top shows that socket memory uncharging path is hot:
> 2.13% [kernel] [k] page_counter_cancel
> 1.14% [kernel] [k] __sk_mem_reduce_allocated
> 1.14% [kernel] [k] _raw_spin_lock
> 0.87% [kernel] [k] _raw_spin_lock_irqsave
> 0.84% [kernel] [k] tcp_ack
> 0.84% [kernel] [k] ixgbe_poll
> 0.83% < workload >
> 0.82% [kernel] [k] enqueue_entity
> 0.68% [kernel] [k] __fget
> 0.68% [kernel] [k] tcp_delack_timer_handler
> 0.67% [kernel] [k] __schedule
> 0.60% < workload >
> 0.59% [kernel] [k] __inet6_lookup_established
> 0.55% [kernel] [k] __switch_to
> 0.55% [kernel] [k] menu_select
> 0.54% libc-2.20.so [.] __memcpy_avx_unaligned
>
> To address this issue, the existing per-cpu stock infrastructure
> can be used.
>
> refill_stock() can be called from mem_cgroup_uncharge_skmem()
> to move charge to a per-cpu stock instead of calling atomic
> page_counter_uncharge().
>
> To prevent the uncontrolled growth of per-cpu stocks,
> refill_stock() will explicitly drain the cached charge,
> if the cached value exceeds CHARGE_BATCH.
>
> This allows significantly optimize the load:
> 1.21% [kernel] [k] _raw_spin_lock
> 1.01% [kernel] [k] ixgbe_poll
> 0.92% [kernel] [k] _raw_spin_lock_irqsave
> 0.90% [kernel] [k] enqueue_entity
> 0.86% [kernel] [k] tcp_ack
> 0.85% < workload >
> 0.74% perf-11120.map [.] 0x000000000061bf24
> 0.73% [kernel] [k] __schedule
> 0.67% [kernel] [k] __fget
> 0.63% [kernel] [k] __inet6_lookup_established
> 0.62% [kernel] [k] menu_select
> 0.59% < workload >
> 0.59% [kernel] [k] __switch_to
> 0.57% libc-2.20.so [.] __memcpy_avx_unaligned
>
> Signed-off-by: Roman Gushchin <guro@fb.com>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Cc: Michal Hocko <mhocko@kernel.org>
> Cc: Vladimir Davydov <vdavydov.dev@gmail.com>
> Cc: cgroups@vger.kernel.org
> Cc: kernel-team@fb.com
> Cc: linux-mm@kvack.org
> Cc: linux-kernel@vger.kernel.org
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
Neat!
As far as other types of pages go: page cache and anon are already
batched pretty well, but I think kmem might benefit from this
too. Have you considered using the stock in memcg_kmem_uncharge()?
--
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>
next prev parent reply other threads:[~2017-08-29 19:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 10:01 [PATCH] mm: memcontrol: use per-cpu stocks for socket memory uncharging Roman Gushchin
2017-08-29 19:26 ` Johannes Weiner [this message]
2017-08-30 10:55 ` Roman Gushchin
2017-09-07 18:44 ` Shakeel Butt
2017-09-07 18:47 ` Roman Gushchin
2017-09-07 19:43 ` Shakeel Butt
2017-08-30 10:57 ` Roman Gushchin
2017-08-30 12:36 ` Michal Hocko
2017-08-30 12:44 ` Roman Gushchin
2017-08-30 12:55 ` Michal Hocko
2017-08-30 12:57 ` Roman Gushchin
2017-08-30 14:23 ` Michal Hocko
2017-08-30 14:24 ` Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170829192621.GA5447@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=vdavydov.dev@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).