From: Dan Williams <dan.j.williams@intel.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Logan Gunthorpe <logang@deltatee.com>,
Juergen Gross <jgross@suse.com>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
xen-devel <xen-devel@lists.xenproject.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH v5 2/3] memremap: rename MEMORY_DEVICE_DEVDAX to MEMORY_DEVICE_GENERIC
Date: Thu, 24 Sep 2020 12:02:40 -0700 [thread overview]
Message-ID: <CAPcyv4isGqsNXqz7tmVbu3UZMNSpZUphCKUkyBMgWYwv5o6OLw@mail.gmail.com> (raw)
In-Reply-To: <20200901083326.21264-3-roger.pau@citrix.com>
On Tue, Sep 1, 2020 at 1:33 AM Roger Pau Monne <roger.pau@citrix.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.
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ira Weiny <ira.weiny@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>, Jason Gunthorpe <jgg@ziepe.ca>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Johannes Thumshirn <jthumshirn@suse.de>,
Logan Gunthorpe <logang@deltatee.com>,
Juergen Gross <jgross@suse.com>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
xen-devel <xen-devel@lists.xenproject.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH v5 2/3] memremap: rename MEMORY_DEVICE_DEVDAX to MEMORY_DEVICE_GENERIC
Date: Thu, 24 Sep 2020 12:02:40 -0700 [thread overview]
Message-ID: <CAPcyv4isGqsNXqz7tmVbu3UZMNSpZUphCKUkyBMgWYwv5o6OLw@mail.gmail.com> (raw)
In-Reply-To: <20200901083326.21264-3-roger.pau@citrix.com>
On Tue, Sep 1, 2020 at 1:33 AM Roger Pau Monne <roger.pau@citrix.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.
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ira Weiny <ira.weiny@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Johannes Thumshirn <jthumshirn@suse.de>,
Logan Gunthorpe <logang@deltatee.com>,
Juergen Gross <jgross@suse.com>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
xen-devel <xen-devel@lists.xenproject.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH v5 2/3] memremap: rename MEMORY_DEVICE_DEVDAX to MEMORY_DEVICE_GENERIC
Date: Thu, 24 Sep 2020 12:02:40 -0700 [thread overview]
Message-ID: <CAPcyv4isGqsNXqz7tmVbu3UZMNSpZUphCKUkyBMgWYwv5o6OLw@mail.gmail.com> (raw)
In-Reply-To: <20200901083326.21264-3-roger.pau@citrix.com>
On Tue, Sep 1, 2020 at 1:33 AM Roger Pau Monne <roger.pau@citrix.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.
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ira Weiny <ira.weiny@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Johannes Thumshirn <jthumshirn@suse.de>,
Logan Gunthorpe <logang@deltatee.com>,
Juergen Gross <jgross@suse.com>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
xen-devel <xen-devel@lists.xenproject.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH v5 2/3] memremap: rename MEMORY_DEVICE_DEVDAX to MEMORY_DEVICE_GENERIC
Date: Thu, 24 Sep 2020 12:02:40 -0700 [thread overview]
Message-ID: <CAPcyv4isGqsNXqz7tmVbu3UZMNSpZUphCKUkyBMgWYwv5o6OLw@mail.gmail.com> (raw)
In-Reply-To: <20200901083326.21264-3-roger.pau@citrix.com>
On Tue, Sep 1, 2020 at 1:33 AM Roger Pau Monne <roger.pau@citrix.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.
next prev parent reply other threads:[~2020-09-24 19:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 8:33 [PATCH v5 0/3] xen/balloon: fixes for memory hotplug Roger Pau Monne
2020-09-01 8:33 ` [PATCH v5 1/3] xen/balloon: add header guard Roger Pau Monne
2020-09-01 8:33 ` [PATCH v5 2/3] memremap: rename MEMORY_DEVICE_DEVDAX to MEMORY_DEVICE_GENERIC Roger Pau Monne
2020-09-01 8:33 ` Roger Pau Monne
2020-09-01 8:54 ` Pankaj Gupta
2020-09-01 8:54 ` Pankaj Gupta
2020-09-01 8:54 ` Pankaj Gupta
2020-09-24 19:02 ` Dan Williams [this message]
2020-09-24 19:02 ` Dan Williams
2020-09-24 19:02 ` Dan Williams
2020-09-24 19:02 ` Dan Williams
2020-09-01 8:33 ` [PATCH v5 3/3] xen: add helpers to allocate unpopulated memory Roger Pau Monne
2020-09-01 8:33 ` Roger Pau Monne
2020-09-01 8:33 ` Roger Pau Monne
2020-09-01 13:37 ` kernel test robot
2020-09-01 13:37 ` kernel test robot
2020-09-01 14:45 ` Roger Pau Monné
2020-09-01 14:45 ` Roger Pau Monné
2020-09-01 14:54 ` Jürgen Groß
2020-09-01 14:54 ` Jürgen Groß
2020-09-03 15:30 ` Jürgen Groß
2020-09-03 15:30 ` Jürgen Groß
2020-09-03 16:38 ` Roger Pau Monné
2020-09-03 16:38 ` Roger Pau Monné
2020-09-04 7:00 ` Jürgen Groß
2020-09-04 7:00 ` Jürgen Groß
2020-09-04 8:42 ` Roger Pau Monné
2020-09-04 8:42 ` Roger Pau Monné
2020-09-04 12:40 ` Jürgen Groß
2020-09-04 12:40 ` Jürgen Groß
2020-09-04 12:40 ` [PATCH v5 0/3] xen/balloon: fixes for memory hotplug Jürgen Groß
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=CAPcyv4isGqsNXqz7tmVbu3UZMNSpZUphCKUkyBMgWYwv5o6OLw@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=jgg@ziepe.ca \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=logang@deltatee.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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.