Linux CXL
 help / color / mirror / Atom feed
From: Gregory Price <gourry@gourry.net>
To: "Huang, Ying" <ying.huang@linux.alibaba.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Davidlohr Bueso <dave@stgolabs.net>,
	dave.jiang@intel.com, alison.schofield@intel.com,
	ira.weiny@intel.com, vishal.l.verma@intel.com,
	seven.yi.lee@gmail.com, hch@infradead.org,
	a.manzanares@samsung.com, fan.ni@samsung.com,
	linux-cxl@vger.kernel.org
Subject: Re: Deep flush support for CXL pmem?
Date: Fri, 17 Oct 2025 10:25:26 -0400	[thread overview]
Message-ID: <aPJR1ihx1j3UqUjx@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <87zf9qf46z.fsf@DESKTOP-5N7EMDA>

On Fri, Oct 17, 2025 at 02:11:16PM +0800, Huang, Ying wrote:
> Hi, All,
> 
> When reading the documentation of PMDK (https://github.com/pmem/pmdk), I
> found that deep flush is used for data loss recovery in addition to GPF.
> With that, we can identify that a file isn't affected by the GPF failure
> because it wasn't opened during the GPF failure.
> 
> However, IIUC, the Linux kernel doesn't support deep flush (via
> nvdimm_flush()) for CXL pmem at least for now.  For NVDIMM, we have WPQ,
> but it appears that we don't have that for CXL.  Is deep flush for CXL
> defined in some spec?
>

Should note that this is relevant not just for pmem, but also for shared
memory use cases.  Last I looked there's nothing defined / implemented.

When I reviewed the cxl.mem protocol about a year or so ago, I came away
thinking a deep flush was going to be problematic for shared devices
(multiple separate coherency domains / non-coherent memory).

~Gregory

  reply	other threads:[~2025-10-17 14:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17  6:11 Deep flush support for CXL pmem? Huang, Ying
2025-10-17 14:25 ` Gregory Price [this message]
2025-10-17 17:00   ` Jonathan Cameron
2025-10-17 19:10 ` dan.j.williams
2025-10-20  2:38   ` Davidlohr Bueso
2025-10-20 11:14   ` Huang, Ying

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=aPJR1ihx1j3UqUjx@gourry-fedora-PF4VCD3F \
    --to=gourry@gourry.net \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=a.manzanares@samsung.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=fan.ni@samsung.com \
    --cc=hch@infradead.org \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=seven.yi.lee@gmail.com \
    --cc=vishal.l.verma@intel.com \
    --cc=ying.huang@linux.alibaba.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