public inbox for cgroups@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <hawk@kernel.org>
To: Yosry Ahmed <yosryahmed@google.com>
Cc: "Christoph Lameter (Ampere)" <cl@linux.com>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	tj@kernel.org, cgroups@vger.kernel.org, hannes@cmpxchg.org,
	lizefan.x@bytedance.com, longman@redhat.com,
	kernel-team@cloudflare.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] cgroup/rstat: Avoid thundering herd problem by kswapd across NUMA nodes
Date: Thu, 27 Jun 2024 11:21:38 +0200	[thread overview]
Message-ID: <cf6eac6b-c75f-4879-a9e5-bb8507879900@kernel.org> (raw)
In-Reply-To: <CAJD7tkauPM5trAhgYSC5_S_wvOA9gozPeUot-yhAW0fbF+Msag@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2678 bytes --]


On 27/06/2024 00.07, Yosry Ahmed wrote:
> On Wed, Jun 26, 2024 at 2:35 PM Jesper Dangaard Brouer <hawk@kernel.org> wrote:
>>
>> On 26/06/2024 00.59, Yosry Ahmed wrote:
>>> On Tue, Jun 25, 2024 at 3:35 PM Christoph Lameter (Ampere) <cl@linux.com> wrote:
>>>>
>>>> On Tue, 25 Jun 2024, Yosry Ahmed wrote:
>>>>
[...]
>>
>> I implemented a variant using completions as Yosry asked for:
>>
>> [V3] https://lore.kernel.org/all/171943668946.1638606.1320095353103578332.stgit@firesoul/
> 
> Thanks! I will take a look at this a little bit later. I am wondering
> if you could verify if that solution fixes the problem with kswapd
> flushing?

I will deploy V3 on some production metals and report back in that thread.

For this patch V2, I already have some results that show it solves the
kswapd lock contention. Attaching grafana screenshot comparing two
machines without/with this V2 patch. Green (16m1253) without patch, and
Yellow line (16m1254) with patched kernel.  These machines have 12 NUMA
nodes and thus 12 kswapd threads, and CPU time is summed for these threads.

Zooming in with perf record we can also see the lock contention is gone.
  - sudo perf record -g -p $(pgrep -d, kswapd) -F 499 sleep 60
  - sudo perf report --no-children  --call-graph graph,0.01,callee 
--sort symbol


On a machine (16m1254) with this V2 patch:

  Samples: 7K of event 'cycles:P', Event count (approx.): 61228473670
    Overhead  Symbol
  +    8.28%  [k] mem_cgroup_css_rstat_flush
  +    6.69%  [k] xfs_perag_get_tag
  +    6.51%  [k] radix_tree_next_chunk
  +    5.09%  [k] queued_spin_lock_slowpath
  +    3.94%  [k] srso_alias_safe_ret
  +    3.62%  [k] srso_alias_return_thunk
  +    3.11%  [k] super_cache_count
  +    2.96%  [k] mem_cgroup_iter
  +    2.95%  [k] down_read_trylock
  +    2.48%  [k] shrink_lruvec
  +    2.12%  [k] isolate_lru_folios
  +    1.76%  [k] dentry_lru_isolate
  +    1.74%  [k] radix_tree_gang_lookup_tag


On a machine (16m1253) without patch:

  Samples: 65K of event 'cycles:P', Event count (approx.): 492125554022
    Overhead  SymbolCoverage]
  +   55.84%  [k] queued_spin_lock_slowpath
    - 55.80% queued_spin_lock_slowpath
       + 53.10% __cgroup_rstat_lock
       + 2.63% evict
  +    7.06%  [k] mem_cgroup_css_rstat_flush
  +    2.07%  [k] page_vma_mapped_walk
  +    1.76%  [k] invalid_folio_referenced_vma
  +    1.72%  [k] srso_alias_safe_ret
  +    1.37%  [k] shrink_lruvec
  +    1.23%  [k] srso_alias_return_thunk
  +    1.17%  [k] down_read_trylock
  +    0.98%  [k] perf_adjust_freq_unthr_context
  +    0.97%  [k] super_cache_count

I think this (clearly) shows that the patch works and eliminates kswapd
lock contention.

--Jesper

[-- Attachment #2: kswapd-cpu-time-patchV2-compare-24h.png --]
[-- Type: image/png, Size: 419959 bytes --]

  reply	other threads:[~2024-06-27  9:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-24 11:55 [PATCH V2] cgroup/rstat: Avoid thundering herd problem by kswapd across NUMA nodes Jesper Dangaard Brouer
2024-06-24 12:46 ` Yosry Ahmed
2024-06-24 17:32   ` Shakeel Butt
2024-06-24 17:40     ` Yosry Ahmed
2024-06-24 19:29       ` Shakeel Butt
2024-06-24 19:37         ` Yosry Ahmed
2024-06-24 20:18           ` Shakeel Butt
2024-06-24 21:43             ` Yosry Ahmed
2024-06-24 22:17               ` Shakeel Butt
2024-06-24 22:21                 ` Yosry Ahmed
2024-06-25  0:24                   ` Shakeel Butt
2024-06-25  9:28                     ` Yosry Ahmed
2024-06-25 15:32                       ` Jesper Dangaard Brouer
2024-06-25 16:00                         ` Yosry Ahmed
2024-06-25 16:21                           ` Shakeel Butt
2024-06-25 20:45                             ` Yosry Ahmed
2024-06-25 21:20                               ` Shakeel Butt
2024-06-25 21:24                                 ` Yosry Ahmed
2024-06-25 22:35                                   ` Christoph Lameter (Ampere)
2024-06-25 22:59                                     ` Yosry Ahmed
2024-06-26 21:35                                       ` Jesper Dangaard Brouer
2024-06-26 22:07                                         ` Yosry Ahmed
2024-06-27  9:21                                           ` Jesper Dangaard Brouer [this message]
2024-06-27 10:36                                             ` Yosry Ahmed

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=cf6eac6b-c75f-4879-a9e5-bb8507879900@kernel.org \
    --to=hawk@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=cl@linux.com \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@cloudflare.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lizefan.x@bytedance.com \
    --cc=longman@redhat.com \
    --cc=shakeel.butt@linux.dev \
    --cc=tj@kernel.org \
    --cc=yosryahmed@google.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