[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPcyv4isGqsNXqz7tmVbu3UZMNSpZUphCKUkyBMgWYwv5o6OLw@mail.gmail.com>
Date: Thu, 24 Sep 2020 12:02:40 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Roger Pau Monne <roger.pau@...rix.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ira Weiny <ira.weiny@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Vishal Verma <vishal.l.verma@...el.com>,
Dave Jiang <dave.jiang@...el.com>,
Jason Gunthorpe <jgg@...pe.ca>,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.ibm.com>,
Johannes Thumshirn <jthumshirn@...e.de>,
Logan Gunthorpe <logang@...tatee.com>,
Juergen Gross <jgross@...e.com>,
linux-nvdimm <linux-nvdimm@...ts.01.org>,
xen-devel <xen-devel@...ts.xenproject.org>,
Linux MM <linux-mm@...ck.org>
Subject: Re: [PATCH v5 2/3] memremap: rename MEMORY_DEVICE_DEVDAX to MEMORY_DEVICE_GENERIC
On Tue, Sep 1, 2020 at 1:33 AM Roger Pau Monne <roger.pau@...rix.com> wrote:
>
> This is in preparation for the logic behind MEMORY_DEVICE_DEVDAX also
> being used by non DAX devices.
>
FWIW I would not call this MEMORY_DEVICE_GENERIC. This is really
MEMORY_DEVICE_SIMPLE and the kernel-doc can clarify in contrast to the
other MEMORY_DEVICE types this type implies no need for driver or
filesystem notification when a page goes idle.
Powered by blists - more mailing lists