From: Yoshimi Ichiyanagi <ichiyanagi.yoshimi@lab.ntt.co.jp>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>
Subject: Re: dax: enable DAX PMD suport for NVDIMM device
Date: Thu, 09 Feb 2017 15:19:48 +0900 [thread overview]
Message-ID: <A45D2829C83A77AAD59E3A1@lab.ntt.co.jp> (raw)
In-Reply-To: <CAPcyv4h4HTJmkneOAeFrhc8HM8RRp43F7nESMY53AP2mZOm5cg@mail.gmail.com>
Thank you, I could enable DAX PMD suport for HPE NVDIMM modules.
The following ndctl command changed the nvdimm device type
from "namespace_io_device_type" to "nd_pfn_device_type", right?
I did the following:
------
# ndctl create-namespace --reconfig=namespace1.0 --mode=memory --force
{
"dev":"namespace1.0",
"mode":"memory",
"size":33820770304,
"uuid":"XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"blockdev":"pmem1"
}
# ndctl list --namespaces
{
"provider":"ACPI.NFIT",
"dev":"ndbus0",
"namespaces":[
{
"dev":"namespace1.0",
"mode":"memory",
"size":33820770304,
"uuid":"XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"blockdev":"pmem1"
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":34359738368,
"blockdev":"pmem0"
}
]
}
#
------
><dan.j.williams@intel.com> wrote:
>You can achieve the same by putting your namespace into "memory" mode
>with the following ndctl command. Note that this will destroy the
>current contents of the namespace, and you must unmount /dev/pmem1
>before running this.
>
> ndctl create-namespace --reconfig=namespace1.0 --mode=memory --force
>
>This arranges for struct page / memmap entries to be created for the
>namespace.
>
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2017-02-09 6:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 2:45 dax: enable DAX PMD suport for NVDIMM device Yoshimi Ichiyanagi
2017-02-09 3:14 ` Dan Williams
2017-02-09 6:19 ` Yoshimi Ichiyanagi [this message]
2017-02-09 19:05 ` Dan Williams
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=A45D2829C83A77AAD59E3A1@lab.ntt.co.jp \
--to=ichiyanagi.yoshimi@lab.ntt.co.jp \
--cc=dan.j.williams@intel.com \
--cc=linux-nvdimm@ml01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.