[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241023032744.84a6a9f6f5f1e3aa1fe5f0d9@linux-foundation.org>
Date: Wed, 23 Oct 2024 03:27:44 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Kairui Song <kasong@...cent.com>
Cc: Kairui Song <ryncsn@...il.com>, linux-mm@...ck.org, Chris Li
<chrisl@...nel.org>, Barry Song <v-songbaohua@...o.com>, Ryan Roberts
<ryan.roberts@....com>, Hugh Dickins <hughd@...gle.com>, Yosry Ahmed
<yosryahmed@...gle.com>, "Huang, Ying" <ying.huang@...el.com>, Tim Chen
<tim.c.chen@...ux.intel.com>, Nhat Pham <nphamcs@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/13] mm, swap: rework of swap allocator locks
On Wed, 23 Oct 2024 03:24:38 +0800 Kairui Song <ryncsn@...il.com> wrote:
> After this series, lock contention on si->lock is nearly unobservable
> with `perf lock` with the same test above :
>
> contended total wait max wait avg wait type caller
> ... snip ...
> 91 204.62 us 4.51 us 2.25 us spinlock cluster_move+0x2e
> ... snip ...
> 47 125.62 us 4.47 us 2.67 us spinlock cluster_move+0x2e
> ... snip ...
> 23 63.15 us 3.95 us 2.74 us spinlock cluster_move+0x2e
> ... snip ...
> 17 41.26 us 4.58 us 2.43 us spinlock cluster_isolate_lock+0x1d
> ... snip ...
Were any overall runtime benefits observed?
Powered by blists - more mailing lists