From: Jeff Moyer <jmoyer@redhat.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: linux-nvdimm@lists.01.org
Subject: Re: [RFC PATCH] libnvdimm: Update the meaning for persistence_domain values
Date: Wed, 15 Jan 2020 12:42:42 -0500 [thread overview]
Message-ID: <x49ftggobu5.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <0f44df90-1f75-9d0a-10af-6e7f48158bc7@linux.ibm.com> (Aneesh Kumar K. V.'s message of "Wed, 15 Jan 2020 23:01:15 +0530")
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com> writes:
>> /*
>> * Platform provides mechanisms to flush outstanding write data
>> * to pmem on system power loss.
>> */
>>
>
> Wanted to add more details. So with the above interpretation, if the
> persistence_domain is found to be 'cpu_cache', application can expect
> a store instruction to guarantee persistence. If it is 'none' there is
> no persistence ( I am not sure how that is the difference from
> 'volatile' pmem region). If it is 'memory_controller' ( I am not sure
> whether that is the right term), application needs to follow the
> recommended mechanism to flush write data to pmem.
There is no enum for "NONE". If there is no persistence domain
specified, then it is undefined/unknown, which results in the message:
nd_pmem namespace0.0: unable to guarantee persistence of writes
Other than that, yes, that's right.
-Jeff
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
next prev parent reply other threads:[~2020-01-15 17:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 6:49 [RFC PATCH] libnvdimm: Update the meaning for persistence_domain values Aneesh Kumar K.V
2020-01-15 16:55 ` Jeff Moyer
2020-01-15 17:27 ` Aneesh Kumar K.V
2020-01-15 17:31 ` Aneesh Kumar K.V
2020-01-15 17:42 ` Jeff Moyer [this message]
2020-01-15 19:44 ` Dan Williams
2020-01-15 17:35 ` Jeff Moyer
2020-01-15 17:55 ` Aneesh Kumar K.V
2020-01-15 19:48 ` Dan Williams
2020-01-16 6:24 ` Aneesh Kumar K.V
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=x49ftggobu5.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=linux-nvdimm@lists.01.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;
as well as URLs for NNTP newsgroup(s).