From: Ira Weiny <ira.weiny@intel.com>
To: Michal Clapinski <mclapinski@google.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Dan Williams <dan.j.williams@intel.com>,
"Vishal Verma" <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
"Ira Weiny" <ira.weiny@intel.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: <nvdimm@lists.linux.dev>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Michal Clapinski <mclapinski@google.com>
Subject: Re: [PATCH v2 1/1] libnvdimm/e820: Add a new parameter to configure many regions per e820 entry
Date: Sun, 20 Apr 2025 21:06:48 -0500 [thread overview]
Message-ID: <6805a8382627f_18b6012946a@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20250417142525.78088-1-mclapinski@google.com>
Michal Clapinski wrote:
> Currently, the user has to specify each memory region to be used with
> nvdimm via the memmap parameter. Due to the character limit of the
> command line, this makes it impossible to have a lot of pmem devices.
> This new parameter solves this issue by allowing users to divide
> one e820 entry into many nvdimm regions.
>
> This change is needed for the hypervisor live update. VMs' memory will
> be backed by those emulated pmem devices. To support various VM shapes
> I want to create devdax devices at 1GB granularity similar to hugetlb.
Why is it not sufficient to create a region out of a single memmap range
and create multiple 1G dax devices within that single range?
Ira
>
> It's also possible to expand this parameter in the future,
> e.g. to specify the type of the device (fsdax/devdax).
>
> Signed-off-by: Michal Clapinski <mclapinski@google.com>
[snip]
next prev parent reply other threads:[~2025-04-21 2:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 14:25 [PATCH v2 1/1] libnvdimm/e820: Add a new parameter to configure many regions per e820 entry Michal Clapinski
2025-04-21 2:06 ` Ira Weiny [this message]
2025-04-21 14:55 ` Pasha Tatashin
2025-05-27 13:25 ` Mike Rapoport
2025-05-28 14:53 ` Pasha Tatashin
2025-04-21 23:20 ` Dan Williams
2025-04-22 13:10 ` Pasha Tatashin
2025-04-22 19:00 ` Dan Williams
2025-04-22 19:40 ` 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=6805a8382627f_18b6012946a@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mclapinski@google.com \
--cc=nvdimm@lists.linux.dev \
--cc=pasha.tatashin@soleen.com \
--cc=vishal.l.verma@intel.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).