From: Yiannis Nikolakopoulos <yi.nikolakop@gmail.com>
To: lsf-pc@lists.linux-foundation.org,
Adam Manzanares <a.manzanares@samsung.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
Angelos Arelakis <angelos.arelakis@zptcorp.com>,
"Weiny, Ira" <ira.weiny@intel.com>,
yiannis@zptcorp.com
Subject: [Resend LSF/MM/BPF TOPIC] A case of a CXL compressed memory tier
Date: Tue, 14 May 2024 13:43:29 +0200 [thread overview]
Message-ID: <CA+CExOi4v_8KM1ZA=ou3uZjpJDnMrJSsCVoWJcoBqbAequzH0g@mail.gmail.com> (raw)
Resending this from my private email to make sure it conforms with the
mailing list etiquette.
Hello all,
This is almost literally last minute and the work itself is only
getting started. But since I'm virtually attending, I thought to give
it a shot in case it is of interest.
Background: at ZeroPoint Technologies we are developing inline memory
compression IP. Currently we are focusing on CXL type 3 devices
(memory expanders), effectively introducing a compressed memory tier
(i.e. fulfilling the OCP specification "Hyperscale CXL Tiered Memory
Expander Specification”).
To utilize the memory saved due to compression, we oversubscribe the
Device Physical Address Space (DPA) in addition to some custom .io
interfaces. If there is interest, I would be glad to present these
APIs and how the host's point of view changes compared to a "typical"
memory tiering system. The goal would be to get some early feedback
and direction for our upstream driver development, before we start
pushing the first RFCs.
Best regards,
Yiannis Nikolakopoulos
next reply other threads:[~2024-05-14 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240514114400uscas1p1e3b27c6da724deb16bf86e4052f29fe4@uscas1p1.samsung.com>
2024-05-14 11:43 ` Yiannis Nikolakopoulos [this message]
2024-05-14 12:30 ` [Resend LSF/MM/BPF TOPIC] A case of a CXL compressed memory tier Adam Manzanares
2024-05-19 10:37 ` Viacheslav Dubeyko
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='CA+CExOi4v_8KM1ZA=ou3uZjpJDnMrJSsCVoWJcoBqbAequzH0g@mail.gmail.com' \
--to=yi.nikolakop@gmail.com \
--cc=a.manzanares@samsung.com \
--cc=angelos.arelakis@zptcorp.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=yiannis@zptcorp.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 read-only IMAP folder(s) and NNTP newsgroup(s).