mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gregory Price <gourry@gourry.net>
To: Haifeng Xu <haifeng.xu@shopee.com>
Cc: rafael@kernel.org, lenb@kernel.org, dan.j.williams@intel.com,
	jonathan.cameron@huawei.com, dave@stgolabs.net,
	dave.jiang@intel.com, alison.schofield@intel.com,
	vishal.l.verma@intel.com, ira.weiny@intel.com,
	linux-cxl@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: add a boot parameter to disable parsing CFMWS during NUMA init
Date: Wed, 4 Mar 2026 12:16:00 -0500	[thread overview]
Message-ID: <aaho0IyQ0WAjcRMM@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <20260304080647.169434-1-haifeng.xu@shopee.com>

On Wed, Mar 04, 2026 at 04:06:47PM +0800, Haifeng Xu wrote:
> For the machine Intel(R) Xeon(R) 6746E that supports CXL memory,
> the possible nodes are 20 (0-19). However, only two numa nodes (0-1)
> have memory and the rest nodes (2-19) detected by CEDT are memoryless.
> 
> The problems is that when creating many pods, the shrinker map size
> needs to be expanded for all memory cgroups in expand_shrinker_info().
> If the number of possible nodes is too large, the holding time of
> shrinker lock grows significantly.
> 
> In this case, there is no CXL memory inserted in the machine, those
> memoryless nodes are useless for us, so there is no need to set them
> in 'numa_nodes_parsed'. After disabling parsing CFMWS, the pod creation
> time is reduced from over 10 minutes to approximately 150 seconds in
> our internal test.
> 

This seems like the wrong scope to fix the underlying problem - which is
the shrinker lock holding scope.

If you're not actually using CXL, can't you just disable CXL in the
BIOS?  Then you shouldn't even emit CFMWS at all.

~Gregory

  parent reply	other threads:[~2026-03-04 17:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04  8:06 Haifeng Xu
2026-03-04 14:10 ` kernel test robot
2026-03-04 15:11 ` kernel test robot
2026-03-04 17:16 ` Gregory Price [this message]
2026-03-05  4:18   ` Haifeng Xu
2026-03-05  6:30     ` Gregory Price
2026-03-05  7:43       ` Haifeng Xu
2026-03-05 19:57 ` kernel test robot
2026-03-05 20:19 ` kernel test robot
2026-03-05 23:00 ` kernel test robot
  -- strict thread matches above, loose matches on Subject: below --
2026-03-04  6:46 Haifeng Xu
2026-03-04  7:55 ` Haifeng Xu

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=aaho0IyQ0WAjcRMM@gourry-fedora-PF4VCD3F \
    --to=gourry@gourry.net \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=haifeng.xu@shopee.com \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=vishal.l.verma@intel.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

all inboxes | Powered by JetHome®