From: Gregory Price <gregory.price@memverge.com>
To: "Christoph Lameter (Ampere)" <cl@linux.com>
Cc: David Rientjes <rientjes@google.com>,
Matthew Wilcox <willy@infradead.org>,
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>,
SeongJae Park <sj@kernel.org>,
linux-mm@kvack.org
Subject: Re: [RFC] Memory tiering kernel alignment
Date: Fri, 26 Jan 2024 18:03:23 -0500 [thread overview]
Message-ID: <ZbQ6O/hdnL7VyjzD@memverge.com> (raw)
In-Reply-To: <17a45e1e-66c4-08ae-92c7-cef4fb0c4e2c@linux.com>
On Fri, Jan 26, 2024 at 01:06:25PM -0800, Christoph Lameter (Ampere) wrote:
> On Thu, 25 Jan 2024, David Rientjes wrote:
>
> > My dream world would be where we could discuss various use cases for
> > locally attached CXL memory and determine, as a group, what the shared,
> > comprehensive "Linux vision" for it is and do so before LSF/MM/BPF. In a
> > perfect world, we could block out an expanded MM session in Salt Lake City
> > to bring all these concepts together, what approaches sound reasonable vs
> > unreasonable, and leave that conference with a clear understanding of what
> > needs to happen.
>
> I thought the main use of CXL is as a standardized interconnect. We finally
> can link up heterogeneous systems with various types of nodes in larger
> system configuration. As such it could contain processor nodes, memory nodes
> and i/o nodes and allow the setup of powerful systems with large address
> spaces, coprocessors, diverse types of processing etc etc.
if you ask 30 people what the "main use" of CXL is/will be, you will get
30 different answers. We should not try to solve world peace here.
That starts with defining scope, and I think topological details should
be extremely limited for a general tiering system. Otherwise we're
inviting serious trouble.
>
> Well yes this is going to create some work but it looks like an exciting way
> to move forward to more powerful system configurations.
>
> All of this will then be possible then in pretty small configurations of
> just a couple of chips.
>
>
>
next prev parent reply other threads:[~2024-01-26 23:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 18:26 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 [this message]
2024-01-28 20:15 ` David Rientjes
2024-01-29 10:27 ` David Hildenbrand
2024-01-26 20:41 ` Christoph Lameter (Ampere)
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=ZbQ6O/hdnL7VyjzD@memverge.com \
--to=gregory.price@memverge.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=cl@linux.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=sj@kernel.org \
--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