[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aWkm8zVc9zy1w3eM@gourry-fedora-PF4VCD3F>
Date: Thu, 15 Jan 2026 12:42:11 -0500
From: Gregory Price <gourry@...rry.net>
To: "David Hildenbrand (Red Hat)" <david@...nel.org>
Cc: linux-mm@...ck.org, linux-cxl@...r.kernel.org, nvdimm@...ts.linux.dev,
linux-kernel@...r.kernel.org, virtualization@...ts.linux.dev,
kernel-team@...a.com, dan.j.williams@...el.com,
vishal.l.verma@...el.com, dave.jiang@...el.com, mst@...hat.com,
jasowang@...hat.com, xuanzhuo@...ux.alibaba.com,
eperezma@...hat.com, osalvador@...e.de, akpm@...ux-foundation.org
Subject: Re: [PATCH v2 0/5] add runtime hotplug state control
On Thu, Jan 15, 2026 at 06:26:21PM +0100, David Hildenbrand (Red Hat) wrote:
> On 1/15/26 00:50, Gregory Price wrote:
> > The dax kmem driver currently onlines memory automatically during
> > probe using the system's default online policy but provides no way
> > to control or query the entire region state at runtime.
> >
> > This series adds a sysfs interface to control DAX kmem memory
> > hotplug state, and refactors the memory_hotplug paths to make it
> > possible for drivers to request an online type at hotplug time.
>
> Gregory, slow down a bit please. I haven't even had the chance to go through
> your replies on v1.
>
Sorry, i realized your feedback on v1 showed there was just too much
complexity. I would ignore v1 entirely at this point, this version is
significantly simpler.
> I'm currently on PTO and don't have the full day to review stuff :) And boy
> oh boy, do I have a lot of stuff in my inbox.
>
> Maybe given this is the second time the patch subject is suboptimal is
> another sign to slow down a bit? :P
>
Apologies, and I will let this one sit.
~Gregory
Powered by blists - more mailing lists