From: Sasha Levin <sashal@kernel.org>
To: Pavel Tatashin <pasha.tatashin@soleen.com>
Cc: jmorris@namei.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-nvdimm@lists.01.org,
akpm@linux-foundation.org, mhocko@suse.com,
dave.hansen@linux.intel.com, dan.j.williams@intel.com,
keith.busch@intel.com, vishal.l.verma@intel.com,
dave.jiang@intel.com, zwisler@kernel.org,
thomas.lendacky@amd.com, ying.huang@intel.com,
fengguang.wu@intel.com, bp@suse.de, bhelgaas@google.com,
baiyaowei@cmss.chinamobile.com, tiwai@suse.de,
jglisse@redhat.com, david@redhat.com
Subject: Re: [v4 2/2] device-dax: "Hotremove" persistent memory that is used like normal RAM
Date: Thu, 2 May 2019 13:34:19 -0400 [thread overview]
Message-ID: <20190502173419.GA3048@sasha-vm> (raw)
In-Reply-To: <20190501191846.12634-3-pasha.tatashin@soleen.com>
On Wed, May 01, 2019 at 03:18:46PM -0400, Pavel Tatashin wrote:
>It is now allowed to use persistent memory like a regular RAM, but
>currently there is no way to remove this memory until machine is
>rebooted.
>
>This work expands the functionality to also allows hotremoving
>previously hotplugged persistent memory, and recover the device for use
>for other purposes.
>
>To hotremove persistent memory, the management software must first
>offline all memory blocks of dax region, and than unbind it from
>device-dax/kmem driver. So, operations should look like this:
>
>echo offline > echo offline > /sys/devices/system/memory/memoryN/state
This looks wrong :)
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-05-02 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 19:18 [v4 0/2] "Hotremove" persistent memory Pavel Tatashin
2019-05-01 19:18 ` [v4 1/2] device-dax: fix memory and resource leak if hotplug fails Pavel Tatashin
2019-05-01 19:18 ` [v4 2/2] device-dax: "Hotremove" persistent memory that is used like normal RAM Pavel Tatashin
2019-05-02 14:14 ` David Hildenbrand
2019-05-02 14:16 ` Pavel Tatashin
2019-05-02 15:54 ` Dan Williams
2019-05-02 16:47 ` Pavel Tatashin
2019-05-02 17:34 ` Sasha Levin [this message]
2019-05-02 17:44 ` Pavel Tatashin
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=20190502173419.GA3048@sasha-vm \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baiyaowei@cmss.chinamobile.com \
--cc=bhelgaas@google.com \
--cc=bp@suse.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=david@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=jglisse@redhat.com \
--cc=jmorris@namei.org \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mhocko@suse.com \
--cc=pasha.tatashin@soleen.com \
--cc=thomas.lendacky@amd.com \
--cc=tiwai@suse.de \
--cc=vishal.l.verma@intel.com \
--cc=ying.huang@intel.com \
--cc=zwisler@kernel.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).