From: Karim Manaouil <kmanaouil.dev@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Yafang Shao <laoar.shao@gmail.com>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Suren Baghdasaryan <surenb@google.com>,
Christoph Lameter <cl@linux.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Tejun Heo <tj@kernel.org>, Johannes Weiner <hannes@cmpxchg.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Namhyung Kim <namhyung@google.com>,
linux-mm@kvack.org
Subject: Re: MM global locks as core counts quadruple
Date: Wed, 26 Jun 2024 20:38:19 +0100 [thread overview]
Message-ID: <ZnxuK75gJkC2rJwr@ed.ac.uk> (raw)
In-Reply-To: <ZnTrZ9mcAIRodnjx@casper.infradead.org>
On Fri, Jun 21, 2024 at 03:54:31AM +0100, Matthew Wilcox wrote:
> I think a more productive solution to contention on the LRU lock is to
> increase the number of zones. I don't think it's helpful to have a
> 1TB zone of memory. Maybe we should limit each zone to 16GB or so.
> That means we'd need to increase the number of zones we support, but
> I think that's doable.
What do you mean by zones? The usual ZONE_{DMA|DMA32|NORMAL|HIGHMEM}?
But that's historically existed to deal with physical addressing
limitations (e.g. DMA for devices that can't deal with addresses
larger than 16MiB, or HIGHMEM on 32-bits to access physical memory
beyond what could be directly mapped by the kernel).
Maybe you mean turning ZONE_NORMAL into an array with each entry
pointing to a smaller ZONE_NORMAL region of, let's say, 64GiB or smthng.
Or it could be divided by the number of CPUs within the NUMA node and each
CPU will be given one ZONE_NORMAL segment with a fallback list to other CPUs
segments in case it runs out of memory. Does that make sense?
Cheers
Karim
PhD Student
Edinburgh University
next prev parent reply other threads:[~2024-06-26 19:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 0:35 MM global locks as core counts quadruple David Rientjes
2024-06-21 2:01 ` Matthew Wilcox
2024-06-21 2:46 ` Yafang Shao
2024-06-21 2:54 ` Matthew Wilcox
2024-06-26 19:38 ` Karim Manaouil [this message]
2024-06-27 5:36 ` Christoph Lameter (Ampere)
2024-06-21 19:10 ` Tejun Heo
2024-06-21 21:37 ` Namhyung Kim
2024-06-23 17:59 ` Tejun Heo
2024-06-24 21:44 ` David Rientjes
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=ZnxuK75gJkC2rJwr@ed.ac.uk \
--to=kmanaouil.dev@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=dave@stgolabs.net \
--cc=hannes@cmpxchg.org \
--cc=laoar.shao@gmail.com \
--cc=linux-mm@kvack.org \
--cc=namhyung@google.com \
--cc=paulmck@kernel.org \
--cc=rientjes@google.com \
--cc=surenb@google.com \
--cc=tj@kernel.org \
--cc=willy@infradead.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 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).