From: Yiannis Nikolakopoulos <yiannis@zptcorp.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>
Subject: [LSF/MM/BPF TOPIC] A case of a CXL compressed memory tier
Date: Tue, 14 May 2024 03:31:03 +0200 [thread overview]
Message-ID: <CAD-mnDY2T6bYHjk=k6FP1EUmNcvzO5kw64hj2=bb_qSQLsRWAg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]
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
--
Yiannis Nikolakopoulos, PhD
Software Lead
ZeroPoint Technologies <http://www.zptcorp.com/>
Remove the waste.
Release the power.
--
**CONFIDENTIALITY NOTICE:*
*
*The contents of this email message and any
attachments are intended solely for the addressee(s) and may contain
confidential and/or privileged information and may be legally protected
from disclosure. If you are not the intended recipient of this message or
their agent, or if this message has been addressed to you in error, please
immediately alert the sender by reply email and then delete this message
and any attachments. If you are not the intended recipient, you are hereby
notified that any use, dissemination, copying, or storage of this message
or its attachments is strictly prohibited. *
[-- Attachment #2: Type: text/html, Size: 4979 bytes --]
reply other threads:[~2024-05-14 1:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAD-mnDY2T6bYHjk=k6FP1EUmNcvzO5kw64hj2=bb_qSQLsRWAg@mail.gmail.com' \
--to=yiannis@zptcorp.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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.