From: "Christoph Lameter (Ampere)" <cl@linux.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: David Rientjes <rientjes@google.com>,
John Hubbard <jhubbard@nvidia.com>, Zi Yan <ziy@nvidia.com>,
Bharata B Rao <bharata@amd.com>,
Dave Jiang <dave.jiang@intel.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
"Huang, Ying" <ying.huang@intel.com>,
Alistair Popple <apopple@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Mel Gorman <mgorman@suse.de>, Jon Grimm <jon.grimm@amd.com>,
Gregory Price <gourry.memverge@gmail.com>,
Brian Morris <bsmorris@google.com>, Wei Xu <weixugc@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org
Subject: Re: [RFC] Memory tiering kernel alignment
Date: Fri, 26 Jan 2024 12:41:21 -0800 (PST) [thread overview]
Message-ID: <45d850ec-623b-7c07-c266-e948cdbf1f62@linux.com> (raw)
In-Reply-To: <ZbKt7jDN8XI561DO@casper.infradead.org>
On Thu, 25 Jan 2024, Matthew Wilcox wrote:
> We should reject this technology before it harms our kernel and the
> entire industry. There's a reason that SGI died. Nobody wants to buy
> single image machines the size of a data centre.
Some people with big pockets needed these data center sized single image
machines. SGI died because Intel was not able to support large memory
(petabytes!) anymore after they neglected to develop the processor that
they promised contractually to SGI and therefore the tech became unusuable
for the deep pocketed customers.
The Linux kernel worked just fine with petabyte sized address spaces.
There are certainly use cases for large memory pools. They can be created
and have been improvised using RDMA. Basically shifting memory back and
forth into the small memory processor spaces that Intel confined us in by
taking sections of a simulated petabyte sized cross machine "address
space" that is spread over lots of network nodes.
CXL could perhaps allow us to come up with a better solution.
next prev parent reply other threads:[~2024-01-26 20:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 18:26 [RFC] Memory tiering kernel alignment David Rientjes
2024-01-25 18:52 ` Matthew Wilcox
2024-01-25 20:04 ` David Rientjes
2024-01-25 20:19 ` Matthew Wilcox
2024-01-25 21:37 ` David Rientjes
2024-01-25 22:28 ` Gregory Price
2024-01-26 0:16 ` SeongJae Park
2024-01-26 21:06 ` Christoph Lameter (Ampere)
2024-01-26 23:03 ` Gregory Price
2024-01-28 20:15 ` David Rientjes
2024-01-29 10:27 ` David Hildenbrand
2024-01-26 20:41 ` Christoph Lameter (Ampere) [this message]
2024-01-26 0:04 ` SeongJae Park
[not found] ` <tsnp3a6oxglx2siv7aoplo665k7xsigkqtpfm5yiu2r3wvys26@3vntgau4t2gv>
2024-01-26 14:31 ` John Groves
2024-02-29 2:04 ` Davidlohr Bueso
2024-02-29 4:01 ` Bharata B Rao
2024-02-29 18:23 ` SeongJae Park
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=45d850ec-623b-7c07-c266-e948cdbf1f62@linux.com \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=apopple@nvidia.com \
--cc=bharata@amd.com \
--cc=bsmorris@google.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=gourry.memverge@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=jhubbard@nvidia.com \
--cc=jon.grimm@amd.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.org \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
--cc=ziy@nvidia.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;
as well as URLs for NNTP newsgroup(s).