From: Wei Yang <richard.weiyang@gmail.com>
To: Pankaj Gupta <pagupta@redhat.com>
Cc: qemu-devel@nongnu.org,
ross zwisler <ross.zwisler@linux.intel.com>,
xiaoguangrong eric <xiaoguangrong.eric@gmail.com>,
Wei Yang <richardw.yang@linux.intel.com>,
mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] docs/nvdimm: add example on persistent backend setup
Date: Wed, 24 Jul 2019 14:52:28 +0000 [thread overview]
Message-ID: <20190724145228.jkcruug5ikhorycv@master> (raw)
In-Reply-To: <127005664.4113094.1563963451244.JavaMail.zimbra@redhat.com>
On Wed, Jul 24, 2019 at 06:17:31AM -0400, Pankaj Gupta wrote:
>
>>
>> Persistent backend setup requires some knowledge about nvdimm and ndctl
>> tool. Some users report they may struggle to gather these knowledge and
>> have difficulty to setup it properly.
>>
>> Here we provide two examples for persistent backend and gives the link
>> to ndctl. By doing so, user could try it directly and do more
>> investigation on persistent backend setup with ndctl.
>>
>> Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
>> ---
>> docs/nvdimm.txt | 28 ++++++++++++++++++++++++++++
>> 1 file changed, 28 insertions(+)
>>
>> diff --git a/docs/nvdimm.txt b/docs/nvdimm.txt
>> index b531cacd35..baba7a940d 100644
>> --- a/docs/nvdimm.txt
>> +++ b/docs/nvdimm.txt
>> @@ -171,6 +171,32 @@ guest software that this vNVDIMM device contains a
>> region that cannot
>> accept persistent writes. In result, for example, the guest Linux
>> NVDIMM driver, marks such vNVDIMM device as read-only.
>>
>> +Backend File Setup Example
>> +..........................
>> +
>> +Here is two examples for how to setup these persistent backend on
>> +linux, which leverages the tool ndctl [3].
>> +
>> +It is easy to setup DAX device backend file.
>> +
>> +A. DAX device
>> +
>> + ndctl create-namespace -f -e namespace0.0 -m devdax
>> +
>> +The /dev/dax0.0 could be used directly in "mem-path" option.
>> +
>> +For DAX file, it is more than creating the proper namespace. The
>> +block device should be partitioned and mounted (with dax option).
>> +
>> +B. DAX file
>> +
>> + ndctl create-namespace -f -e namespace0.0 -m fsdax
>> + (partition /dev/pmem0 with name pmem0p1)
>> + mount -o dax /dev/pmem0p1 /mnt
>> + (dd a file with proper size in /mnt)
>
>This is not clear to me. why 'dd' file is required in /mnt?
>You mean for creating a backend file?
>
Yes, create a backend file. You need to give a file instead of a directory to
qemu command line.
>> +
>> +Then the new file in /mnt could be used in "mem-path" option.
>> +
>> NVDIMM Persistence
>> ------------------
>>
>> @@ -212,3 +238,5 @@ References
>> https://www.snia.org/sites/default/files/technical_work/final/NVMProgrammingModel_v1.2.pdf
>> [2] Persistent Memory Development Kit (PMDK), formerly known as NVML
>> project, home page:
>> http://pmem.io/pmdk/
>> +[3] ndctl-create-namespace - provision or reconfigure a namespace
>> + http://pmem.io/ndctl/ndctl-create-namespace.html
>> --
>
>Looks good to me. Just a small comment above.
>Other than that: Reviewed-by: Pankaj Gupta <pagupta@redhat.com>
>
Thanks
>> 2.17.1
>>
>>
>>
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2019-07-24 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 7:03 [Qemu-devel] [PATCH] docs/nvdimm: add example on persistent backend setup Wei Yang
2019-07-24 7:28 ` Pankaj Gupta
2019-07-24 8:53 ` Wei Yang
2019-07-24 10:08 ` Pankaj Gupta
2019-07-24 10:17 ` Pankaj Gupta
2019-07-24 14:52 ` Wei Yang [this message]
2019-07-25 4:43 ` Pankaj Gupta
2019-07-25 4:46 ` Pankaj Gupta
2019-07-29 13:58 ` Stefan Hajnoczi
2019-07-30 0:51 ` Wei Yang
2019-07-30 6:03 ` Stefan Hajnoczi
2019-08-01 0:35 ` Wei Yang
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=20190724145228.jkcruug5ikhorycv@master \
--to=richard.weiyang@gmail.com \
--cc=mst@redhat.com \
--cc=pagupta@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richardw.yang@linux.intel.com \
--cc=ross.zwisler@linux.intel.com \
--cc=xiaoguangrong.eric@gmail.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;
as well as URLs for NNTP newsgroup(s).