All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Yoo <harry@kernel.org>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Cc: Tim Menninger <tmenninger@everpuredata.com>,
	linux-mm@kvack.org,  Chuck Lever <cel@kernel.org>,
	linux-nfs@vger.kernel.org, Jon Curley <jcurley@everpuredata.com>,
	 Eric Badger <ebadger@everpuredata.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Hao Li <hao.li@linux.dev>, Christoph Lameter <cl@gentwo.org>,
	 David Rientjes <rientjes@google.com>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	 Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	 Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	 Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	 Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	 Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@linaro.org>,
	 linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [SLUB] nfs_page cmpxchg_double_fail and perf lock perturbation on dual-socket NFS/RDMA
Date: Mon, 21 Sep 2026 16:31:53 +0100	[thread overview]
Message-ID: <arFNKeseUHBvdRCA@thinkstation> (raw)
In-Reply-To: <8705aa4f-5e02-45e7-ad45-0baa982a8c02@kernel.org>

On Fri, Sep 18, 2026 at 09:08:37AM +0200, Vlastimil Babka (SUSE) wrote:
> On 9/17/26 18:25, Tim Menninger wrote:
> > It reproduces with slab_nomerge.
> > 
> > I booted the same kernel with:
> > 
> >     $ cat /proc/cmdline
> >     ... slab_nomerge ...
> > 
> > Uninstrumented throughput remains in the high-45 to low-46 GB/s
> > range, as before. During perf lock it was around 30 GB/s in these
> > runs, versus roughly 25 GB/s previously.
> > 
> > The dominant lock measurements are essentially unchanged:
> > 
> >                          default             slab_nomerge
> >     unpinned/node0
> >       contentions        4,782,839             4,858,759
> >       total wait          14.39 min             14.26 min
> >       average wait       180.47 us             176.13 us
> > 
> >     node0/node0
> >       contentions        4,582,012             4,686,729
> >       total wait          14.13 min             14.34 min
> >       average wait       185.05 us             183.53 us
> > 
> >     unpinned/balanced
> >       contentions        4,572,196             4,544,677
> >       total wait          12.81 min             12.56 min
> >       average wait       168.14 us             165.84 us
> > 
> > The uninstrumented cmpxchg_double_fail deltas were:
> > 
> >                          default     slab_nomerge
> >     unpinned/node0          7,471          8,892
> >     node0/node0               713            457
> >     unpinned/balanced       1,503          1,504
> > 
> > The CPU-utilization change while perf lock is active also remains.
> > System-wide %idle for uninstrumented/instrumented windows was:
> > 
> >                            default                  slab_nomerge
> >                        uninstr.   instr.         uninstr.   instr.
> >     unpinned/node0      31.46%    3.60%           23.02%    2.15%
> >     node0/node0         84.26%   12.07%           84.62%   11.85%
> >     unpinned/balanced   66.86%   14.83%           66.58%   14.78%
> 
> I believe the weirdest part in the original report was how slub stat
> counters such as free_fastpath etc got order of magnitude higher with
> instrumented vs non-instrumented.
> Did any of that change with slab_nomerge?

If it didn't change, that'd be very surprising.
... unless perf lock was writing data to an NFS filesystem?

-- 
Cheers,
Harry / Hyeonggon

  reply	other threads:[~2026-09-21 15:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 23:22 [SLUB] nfs_page cmpxchg_double_fail and perf lock perturbation on dual-socket NFS/RDMA Tim Menninger
2026-09-17 13:46 ` Harry Yoo
2026-09-17 14:10   ` Harry Yoo
2026-09-17 15:29     ` Peter Zijlstra
2026-09-18  7:04       ` Namhyung Kim
2026-09-17 16:25     ` Tim Menninger
2026-09-18  7:08       ` Vlastimil Babka (SUSE)
2026-09-21 15:31         ` Harry Yoo [this message]
2026-09-21 23:27           ` Tim Menninger
2026-09-18  7:14     ` Namhyung Kim

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=arFNKeseUHBvdRCA@thinkstation \
    --to=harry@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=cel@kernel.org \
    --cc=cl@gentwo.org \
    --cc=ebadger@everpuredata.com \
    --cc=hao.li@linux.dev \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jcurley@everpuredata.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    --cc=tmenninger@everpuredata.com \
    --cc=vbabka@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.