linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Yasunori Gotou (Fujitsu)" <y-goto@fujitsu.com>
To: "'Darrick J. Wong'" <djwong@kernel.org>,
	"ruansy.fnst@fujitsu.com" <ruansy.fnst@fujitsu.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>,
	"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	"willy@infradead.org" <willy@infradead.org>,
	"jack@suse.cz" <jack@suse.cz>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: RE: [PATCH v11 2/2] mm, pmem, xfs: Introduce MF_MEM_REMOVE for unbind
Date: Wed, 5 Apr 2023 01:28:21 +0000	[thread overview]
Message-ID: <TYWPR01MB10082AAC981E7D46D41426FE290909@TYWPR01MB10082.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20230404174517.GF109974@frogsfrogsfrogs>

Hello, Darrick-san,

> Also: Is Fujitsu still pursuing pmem products?  Even though Optane is dead?
> I'm no longer sure of what the roadmap is for all this fsdax code and whatnot.

I need to talk about it.

Though Optane is certainly dead, "persistent memory" is not dead.
Because CXL specification supports persistent memory and FS-DAX
should be supported for it.

Actually, one of our customer tried to use Persistent memory for MySQL(*),
and I heard that they still expects CXL Pmem.

(*) https://www.docswell.com/s/ydnjp/K86GY5-2022-03-07-145233#p1

So, please continue.

Thanks,



  reply	other threads:[~2023-04-05  1:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28  9:41 [PATCH v11 0/2] " Shiyang Ruan
2023-03-28  9:41 ` [PATCH v11 1/2] xfs: fix the calculation of length and end Shiyang Ruan
2023-03-28  9:41 ` [PATCH v11 2/2] mm, pmem, xfs: Introduce MF_MEM_REMOVE for unbind Shiyang Ruan
2023-04-04 17:45   ` Darrick J. Wong
2023-04-05  1:28     ` Yasunori Gotou (Fujitsu) [this message]
2023-04-05  4:36     ` Dan Williams
2023-04-06 10:50     ` Shiyang Ruan
2023-04-06 14:54       ` Darrick J. Wong
2023-04-07  2:07         ` Shiyang Ruan
2023-04-12 10:52   ` [RFC PATCH v11.1 " Shiyang Ruan
2023-04-20  2:07     ` Shiyang Ruan
2023-04-20 12:09       ` Jan Kara
2023-04-25 12:47         ` Shiyang Ruan
2023-04-25 13:23           ` Jan Kara
2023-04-25 15:18             ` Darrick J. Wong
2023-04-26  2:27               ` Shiyang Ruan
2023-04-26  2:37                 ` Darrick J. Wong
2023-04-04  4:33 ` [PATCH v11 0/2] " Shiyang Ruan

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=TYWPR01MB10082AAC981E7D46D41426FE290909@TYWPR01MB10082.jpnprd01.prod.outlook.com \
    --to=y-goto@fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=djwong@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=ruansy.fnst@fujitsu.com \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox