From: Gregory Price <gourry@gourry.net>
To: David Hildenbrand <david@redhat.com>
Cc: dan.j.williams@intel.com, nvdimm@lists.linux.dev,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
vishal.l.verma@intel.com, dave.jiang@intel.com,
linux-cxl@vger.kernel.org
Subject: Re: [PATCH] DAX: warn when kmem regions are truncated for memory block alignment.
Date: Tue, 1 Apr 2025 10:43:36 -0400 [thread overview]
Message-ID: <Z-v7mMZcP1JPIuj4@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <3e3115c0-c3a2-4ec2-8aea-ee1b40057dd6@redhat.com>
On Tue, Apr 01, 2025 at 11:33:59AM +0200, David Hildenbrand wrote:
> On 31.03.25 20:27, Gregory Price wrote:
> > We discussed [1] how this auto-sizing can cause 1GB huge page
> > allocation failures (assuming you online as ZONE_NORMAL). That means
> > ACPI-informed sizing by default would potentially be harmful to existing
> > systems and adding yet-another-boot-option just seems nasty.
> >
> > I've since dropped acpi-informed block size patch[2]. If there are opinions
> > otherwise, I can continue pushing it.
>
> Oh, I thought we would be going forward with that. What's the reason we
> would not want to do that?
>
It seemed like having it reduce block size by default would make 1GB huge
pages less reliable to allocate. If you think this isn't a large concern,
I can update and push again. I suppose I could make it a build option.
Any opinions here are welcome.
~Gregory
next prev parent reply other threads:[~2025-04-01 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 18:07 [PATCH] DAX: warn when kmem regions are truncated for memory block alignment Gregory Price
2025-03-31 18:27 ` Gregory Price
2025-04-01 9:33 ` David Hildenbrand
2025-04-01 14:43 ` Gregory Price [this message]
2025-04-01 14:50 ` David Hildenbrand
2025-04-01 15:16 ` Gregory Price
2025-04-01 15:19 ` David Hildenbrand
2025-04-01 15:26 ` Gregory Price
2025-04-01 15:29 ` David Hildenbrand
2025-04-01 9:47 ` David Hildenbrand
2025-04-01 14:44 ` Gregory Price
2025-04-01 17:47 ` Dan Williams
2025-04-01 18:27 ` Gregory Price
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=Z-v7mMZcP1JPIuj4@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=david@redhat.com \
--cc=kernel-team@meta.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--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 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.