From: Andrew Morton <akpm@linux-foundation.org>
To: Alistair Popple <apopple@nvidia.com>
Cc: David Hildenbrand <david@redhat.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-mm@kvack.org, lina@asahilina.net, zhang.lyra@gmail.com,
gerald.schaefer@linux.ibm.com, vishal.l.verma@intel.com,
dave.jiang@intel.com, logang@deltatee.com, bhelgaas@google.com,
jack@suse.cz, jgg@ziepe.ca, catalin.marinas@arm.com,
will@kernel.org, mpe@ellerman.id.au, npiggin@gmail.com,
dave.hansen@linux.intel.com, ira.weiny@intel.com,
willy@infradead.org, djwong@kernel.org, tytso@mit.edu,
linmiaohe@huawei.com, peterx@redhat.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, nvdimm@lists.linux.dev,
linux-cxl@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
jhubbard@nvidia.com, hch@lst.de, david@fromorbit.com,
sfr@canb.auug.org.au
Subject: Re: [PATCH v3 00/25] fs/dax: Fix ZONE_DEVICE page reference counts
Date: Sun, 15 Dec 2024 22:26:55 -0800 [thread overview]
Message-ID: <20241215222655.ef0b15148120a2e2b06b2234@linux-foundation.org> (raw)
In-Reply-To: <wysuus23bqmjtwkfu3zutqtmkse3ki3erf45x32yezlrl24qto@xlqt7qducyld>
On Mon, 16 Dec 2024 11:55:30 +1100 Alistair Popple <apopple@nvidia.com> wrote:
> The remainder are more -mm focussed. However they do depend on the fs/dax
> cleanups in the first half so the trick would be making sure Andrew only takes
> them if the nvdimm.git changes have made it into -next. I'm happy with either
> approach, so let me know if I should split the series or not.
My inclination is to put it all into the nvdimm tree, with appropriate
MM developer acks.
But I'm having difficulty determining how practical that is because the
v3 series is almost a month old so my test merging was quite ugly.
Perhaps you could prepare a new-doesn't-need-to-be-final version for
people to look at and to aid with this head-scratching?
next prev parent reply other threads:[~2024-12-16 6:27 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 1:40 [PATCH v3 00/25] fs/dax: Fix ZONE_DEVICE page reference counts Alistair Popple
2024-11-22 1:40 ` [PATCH v3 01/25] fuse: Fix dax truncate/punch_hole fault path Alistair Popple
2024-11-22 1:40 ` [PATCH v3 02/25] fs/dax: Return unmapped busy pages from dax_layout_busy_page_range() Alistair Popple
2024-11-22 1:40 ` [PATCH v3 03/25] fs/dax: Don't skip locked entries when scanning entries Alistair Popple
2024-11-22 1:40 ` [PATCH v3 04/25] fs/dax: Refactor wait for dax idle page Alistair Popple
2024-11-22 1:40 ` [PATCH v3 05/25] fs/dax: Create a common implementation to break DAX layouts Alistair Popple
2024-11-22 2:57 ` John Hubbard
2024-11-22 3:37 ` Alistair Popple
2024-11-25 13:27 ` kernel test robot
2024-11-22 1:40 ` [PATCH v3 06/25] fs/dax: Always remove DAX page-cache entries when breaking layouts Alistair Popple
2024-11-22 1:40 ` [PATCH v3 07/25] fs/dax: Ensure all pages are idle prior to filesystem unmount Alistair Popple
2024-11-22 1:40 ` [PATCH v3 08/25] fs/dax: Remove PAGE_MAPPING_DAX_SHARED mapping flag Alistair Popple
2024-11-22 1:40 ` [PATCH v3 09/25] mm/gup.c: Remove redundant check for PCI P2PDMA page Alistair Popple
2024-11-22 1:40 ` [PATCH v3 10/25] pci/p2pdma: Don't initialise page refcount to one Alistair Popple
2024-11-22 18:20 ` Bjorn Helgaas
2024-11-24 22:39 ` Alistair Popple
2024-11-22 1:40 ` [PATCH v3 11/25] mm: Allow compound zone device pages Alistair Popple
2024-11-25 5:05 ` kernel test robot
2024-11-25 15:51 ` kernel test robot
2024-11-22 1:40 ` [PATCH v3 12/25] mm/memory: Enhance insert_page_into_pte_locked() to create writable mappings Alistair Popple
2024-11-22 1:40 ` [PATCH v3 13/25] mm/memory: Add vmf_insert_page_mkwrite() Alistair Popple
2024-11-22 1:40 ` [PATCH v3 14/25] huge_memory: Allow mappings of PUD sized pages Alistair Popple
2024-12-14 15:32 ` David Hildenbrand
2024-11-22 1:40 ` [PATCH v3 15/25] huge_memory: Allow mappings of PMD " Alistair Popple
2024-11-22 1:40 ` [PATCH v3 16/25] memremap: Add is_device_dax_page() and is_fsdax_page() helpers Alistair Popple
2024-11-22 1:40 ` [PATCH v3 17/25] gup: Don't allow FOLL_LONGTERM pinning of FS DAX pages Alistair Popple
2024-11-22 3:23 ` John Hubbard
2024-11-22 1:40 ` [PATCH v3 18/25] proc/task_mmu: Ignore ZONE_DEVICE pages Alistair Popple
2024-11-22 1:40 ` [PATCH v3 19/25] memcontrol-v1: " Alistair Popple
2024-11-22 1:40 ` [PATCH v3 20/25] mm/mlock: Skip ZONE_DEVICE PMDs during mlock Alistair Popple
2024-11-22 1:40 ` [PATCH v3 21/25] fs/dax: Properly refcount fs dax pages Alistair Popple
2024-11-22 1:40 ` [PATCH v3 22/25] device/dax: Properly refcount device dax pages when mapping Alistair Popple
2024-11-22 1:40 ` [PATCH v3 23/25] mm: Remove pXX_devmap callers Alistair Popple
2024-11-22 1:40 ` [PATCH v3 24/25] mm: Remove devmap related functions and page table bits Alistair Popple
2024-11-22 1:40 ` [PATCH v3 25/25] Revert "riscv: mm: Add support for ZONE_DEVICE" Alistair Popple
2024-11-25 13:13 ` Björn Töpel
2024-12-14 1:39 ` [PATCH v3 00/25] fs/dax: Fix ZONE_DEVICE page reference counts Dan Williams
2024-12-14 15:22 ` David Hildenbrand
2024-12-16 0:55 ` Alistair Popple
2024-12-16 6:26 ` Andrew Morton [this message]
2024-12-17 5:20 ` Alistair Popple
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=20241215222655.ef0b15148120a2e2b06b2234@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=david@fromorbit.com \
--cc=david@redhat.com \
--cc=djwong@kernel.org \
--cc=gerald.schaefer@linux.ibm.com \
--cc=hch@lst.de \
--cc=ira.weiny@intel.com \
--cc=jack@suse.cz \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=lina@asahilina.net \
--cc=linmiaohe@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=logang@deltatee.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=nvdimm@lists.linux.dev \
--cc=peterx@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
--cc=vishal.l.verma@intel.com \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=zhang.lyra@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox