[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <680feb78d4923_1d522947b@dwillia2-xfh.jf.intel.com.notmuch>
Date: Mon, 28 Apr 2025 13:56:24 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: <akpm@...ux-foundation.org>
CC: Gregory Price <gourry@...rry.net>, <linux-cxl@...r.kernel.org>,
<nvdimm@...ts.linux.dev>, <linux-kernel@...r.kernel.org>,
<kernel-team@...a.com>, <vishal.l.verma@...el.com>, <dave.jiang@...el.com>,
<jonathan.cameron@...wei.com>, <alison.schofield@...el.com>, "David
Hildenbrand" <david@...hat.com>
Subject: Re: [PATCH v3] DAX: warn when kmem regions are truncated for memory
block alignment.
Gregory Price wrote:
> Device capacity intended for use as system ram should be aligned to the
> architecture-defined memory block size or that capacity will be silently
> truncated and capacity stranded.
>
> As hotplug dax memory becomes more prevelant, the memory block size
> alignment becomes more important for platform and device vendors to
> pay attention to - so this truncation should not be silent.
>
> This issue is particularly relevant for CXL Dynamic Capacity devices,
> whose capacity may arrive in spec-aligned but block-misaligned chunks.
>
> Suggested-by: David Hildenbrand <david@...hat.com>
> Suggested-by: Dan Williams <dan.j.williams@...el.com>
> Reviewed-by: Dan Williams <dan.j.williams@...el.com>
> Tested-by: Alison Schofield <alison.schofield@...el.com>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@...wei.com>
> Acked-by: David Hildenbrand <david@...hat.com>
> Signed-off-by: Gregory Price <gourry@...rry.net>
Hi Andrew, please pick up this patch:
msg-id: 20250410142831.217887-1-gourry@...rry.net
...for -mm. I now notice that MAINTAINERS does not make clear that you
be Cc'd on driver/dax/ patch for eventual upstream merge.
I still support dax patches going through -mm given potential
entanglements.
Powered by blists - more mailing lists