Linux CXL
 help / color / mirror / Atom feed
From: Gregory Price <gregory.price@memverge.com>
To: Adam Manzanares <a.manzanares@samsung.com>
Cc: Mike Rapoport <rppt@kernel.org>,
	Kyungsan Kim <ks0204.kim@samsung.com>,
	"lsf-pc@lists.linux-foundation.org" 
	<lsf-pc@lists.linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
	"viacheslav.dubeyko@bytedance.com"
	<viacheslav.dubeyko@bytedance.com>,
	"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	"seungjun.ha@samsung.com" <seungjun.ha@samsung.com>,
	"wj28.lee@samsung.com" <wj28.lee@samsung.com>
Subject: Re: RE: RE(2): FW: [LSF/MM/BPF TOPIC] SMDK inspired MM changes for CXL
Date: Sat, 1 Apr 2023 06:51:01 -0400	[thread overview]
Message-ID: <ZCgMlc63gnhHgwuD@memverge.com> (raw)
In-Reply-To: <20230404175754.GA633356@bgt-140510-bm01>

On Tue, Apr 04, 2023 at 05:58:05PM +0000, Adam Manzanares wrote:
> On Tue, Apr 04, 2023 at 11:31:08AM +0300, Mike Rapoport wrote:
> > 
> > The point of zswap IIUC is to have small and fast swap device and
> > compression is required to better utilize DRAM capacity at expense of CPU
> > time.
> > 
> > Presuming CXL memory will have larger capacity than DRAM, why not skip the
> > compression and use CXL as a swap device directly?
> 
> I like to shy away from saying CXL memory should be used for swap. I see a 
> swap device as storing pages in a manner that is no longer directly addressable
> by the cpu. 
> 
> Migrating pages to a CXL device is a reasonable approach and I believe we
> have the ability to do this in the page reclaim code. 
> 

The argument is "why do you need swap if memory itself is elastic", and
I think there are open questions about how performant using large
amounts of high-latency memory is.

Think 1us-1.5us+ cross-rack attached memory.

Does it make sense to use that as CPU-addressible and migrate it on
first use?  Isn't that just swap with more steps?  What happens if we
just use it as swap, is the performance all that different?

I think there's a reasonable argument for exploring the idea at the
higher ends of the latency spectrum.  And the simplicity of using an
existing system (swap) to implement a form of proto-tiering is rather
attractive in my opinion.

~Gregory

  reply	other threads:[~2023-04-04 18:43 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230221014114epcas2p1687db1d75765a8f9ed0b3495eab1154d@epcas2p1.samsung.com>
2023-02-21  1:41 ` [LSF/MM/BPF TOPIC] SMDK inspired MM changes for CXL Kyungsan Kim
2023-02-27 23:14   ` Dan Williams
2023-02-28  4:35     ` Kyungsan Kim
2023-03-03  6:07   ` Huang, Ying
2023-03-22  4:33     ` FW: " Kyungsan Kim
2023-03-22 22:03       ` Dan Williams
2023-03-23 10:51         ` RE(2): " Kyungsan Kim
2023-03-23 12:25           ` David Hildenbrand
2023-03-24  9:09             ` RE(4): " Kyungsan Kim
2023-03-24  9:12               ` David Hildenbrand
2023-03-24  9:27                 ` RE(2): " Kyungsan Kim
2023-03-24  9:30                   ` David Hildenbrand
2023-03-24  9:50                     ` RE(3): " Kyungsan Kim
2023-03-24 13:08                       ` Jørgen Hansen
2023-03-24 22:33                         ` David Hildenbrand
2023-03-31 11:42                           ` Kyungsan Kim
2023-03-31 13:42                             ` Matthew Wilcox
2023-03-31 15:56                               ` Frank van der Linden
2023-04-03  8:34                                 ` David Hildenbrand
2023-04-05  2:16                                   ` Kyungsan Kim
2023-04-05  2:06                                 ` Re: " Kyungsan Kim
2023-04-05  5:00                                   ` Dan Williams
2023-04-05  2:01                               ` Kyungsan Kim
2023-04-05  3:11                                 ` Matthew Wilcox
2023-04-03  8:28                             ` David Hildenbrand
2023-04-05  2:09                               ` Kyungsan Kim
2023-03-31 11:31                         ` RE: RE(3): " Kyungsan Kim
2023-03-24  0:41           ` RE(2): " Huang, Ying
2023-03-24  8:48             ` RE(4): " Kyungsan Kim
2023-03-24 13:46               ` Gregory Price
2023-03-31 11:34                 ` Kyungsan Kim
2023-03-31 15:53                   ` Gregory Price
2023-04-05  2:02                     ` Kyungsan Kim
2023-03-24 14:55           ` RE(2): " Matthew Wilcox
2023-03-24 17:49             ` Matthew Wilcox
2023-03-31 11:37               ` Kyungsan Kim
2023-03-31 12:54                 ` Matthew Wilcox
2023-04-05  2:00                   ` Kyungsan Kim
2023-04-05  4:48                     ` Dan Williams
2023-04-05 18:12                       ` Matthew Wilcox
2023-04-05 19:42                         ` Dan Williams
2023-04-06 12:27                           ` David Hildenbrand
2023-04-07  9:30                             ` Kyungsan Kim
2023-03-31 11:38               ` Re: RE(2): " Kyungsan Kim
2023-03-26  7:21           ` Mike Rapoport
2023-03-30 22:03             ` Dragan Stancevic
2023-04-03  8:44               ` Mike Rapoport
2023-04-04  4:27                 ` Dragan Stancevic
2023-04-04  6:47                   ` Huang, Ying
2023-04-06 22:27                     ` Dragan Stancevic
2023-04-07  0:58                       ` Huang, Ying
2023-04-07  9:29                         ` Kyungsan Kim
2023-04-07 14:35                         ` Dragan Stancevic
2023-04-05 10:18                   ` Kyungsan Kim
2023-03-31 11:45             ` RE: RE(2): " Kyungsan Kim
2023-04-04  8:31               ` Mike Rapoport
2023-04-04 17:58                 ` Adam Manzanares
2023-04-01 10:51                   ` Gregory Price [this message]
2023-04-04 18:59                     ` [External] " Viacheslav A.Dubeyko
2023-04-01 11:51                       ` Gregory Price
2023-04-04 21:09                         ` Viacheslav A.Dubeyko
     [not found]                         ` <642cb7ec58c71_21a829453@dwillia2-xfh.jf.intel.com.notmuch>
2023-04-05  2:34                           ` Gregory Price
2023-04-05 10:18                         ` Kyungsan Kim
2023-03-30 22:02   ` Dragan Stancevic
2023-03-31 11:46     ` Kyungsan Kim
2023-04-14  8:41   ` FW: " Kyungsan Kim
2023-05-09 18:45     ` MTK

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=ZCgMlc63gnhHgwuD@memverge.com \
    --to=gregory.price@memverge.com \
    --cc=a.manzanares@samsung.com \
    --cc=dan.j.williams@intel.com \
    --cc=ks0204.kim@samsung.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=rppt@kernel.org \
    --cc=seungjun.ha@samsung.com \
    --cc=viacheslav.dubeyko@bytedance.com \
    --cc=wj28.lee@samsung.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