From: "Darrick J. Wong" <djwong@kernel.org>
To: Shiyang Ruan <ruansy.fnst@fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
nvdimm@lists.linux.dev, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, dan.j.williams@intel.com,
david@fromorbit.com, hch@infradead.org, jane.chu@oracle.com,
rgoldwyn@suse.de, viro@zeniv.linux.org.uk, willy@infradead.org,
naoya.horiguchi@nec.com, linmiaohe@huawei.com
Subject: Re: [PATCHSETS] v14 fsdax-rmap + v11 fsdax-reflink
Date: Tue, 10 May 2022 17:03:52 -0700 [thread overview]
Message-ID: <20220511000352.GY27195@magnolia> (raw)
In-Reply-To: <20220508143620.1775214-1-ruansy.fnst@fujitsu.com>
On Sun, May 08, 2022 at 10:36:06PM +0800, Shiyang Ruan wrote:
> This is a combination of two patchsets:
> 1.fsdax-rmap: https://lore.kernel.org/linux-xfs/20220419045045.1664996-1-ruansy.fnst@fujitsu.com/
> 2.fsdax-reflink: https://lore.kernel.org/linux-xfs/20210928062311.4012070-1-ruansy.fnst@fujitsu.com/
>
> Changes since v13 of fsdax-rmap:
> 1. Fixed mistakes during rebasing code to latest next-
> 2. Rebased to next-20220504
>
> Changes since v10 of fsdax-reflink:
> 1. Rebased to next-20220504 and fsdax-rmap
> 2. Dropped a needless cleanup patch: 'fsdax: Convert dax_iomap_zero to
> iter model'
> 3. Fixed many conflicts during rebasing
> 4. Fixed a dedupe bug in Patch 05: the actuall length to compare could be
> shorter than smap->length or dmap->length.
> PS: There are many changes during rebasing. I think it's better to
> review again.
>
> ==
> Shiyang Ruan (14):
> fsdax-rmap:
> dax: Introduce holder for dax_device
> mm: factor helpers for memory_failure_dev_pagemap
> pagemap,pmem: Introduce ->memory_failure()
> fsdax: Introduce dax_lock_mapping_entry()
> mm: Introduce mf_dax_kill_procs() for fsdax case
Hmm. This patchset touches at least the dax, pagecache, and xfs
subsystems. Assuming it's too late for 5.19, how should we stage this
for 5.20?
I could just add the entire series to iomap-5.20-merge and base the
xfs-5.20-merge off of that? But I'm not sure what else might be landing
in the other subsystems, so I'm open to input.
--D
> xfs: Implement ->notify_failure() for XFS
> fsdax: set a CoW flag when associate reflink mappings
> fsdax-reflink:
> fsdax: Output address in dax_iomap_pfn() and rename it
> fsdax: Introduce dax_iomap_cow_copy()
> fsdax: Replace mmap entry in case of CoW
> fsdax: Add dax_iomap_cow_copy() for dax zero
> fsdax: Dedup file range to use a compare function
> xfs: support CoW in fsdax mode
> xfs: Add dax dedupe support
>
> drivers/dax/super.c | 67 +++++-
> drivers/md/dm.c | 2 +-
> drivers/nvdimm/pmem.c | 17 ++
> fs/dax.c | 398 ++++++++++++++++++++++++++++++------
> fs/erofs/super.c | 13 +-
> fs/ext2/super.c | 7 +-
> fs/ext4/super.c | 9 +-
> fs/remap_range.c | 31 ++-
> fs/xfs/Makefile | 5 +
> fs/xfs/xfs_buf.c | 10 +-
> fs/xfs/xfs_file.c | 9 +-
> fs/xfs/xfs_fsops.c | 3 +
> fs/xfs/xfs_inode.c | 69 ++++++-
> fs/xfs/xfs_inode.h | 1 +
> fs/xfs/xfs_iomap.c | 46 ++++-
> fs/xfs/xfs_iomap.h | 3 +
> fs/xfs/xfs_mount.h | 1 +
> fs/xfs/xfs_notify_failure.c | 220 ++++++++++++++++++++
> fs/xfs/xfs_reflink.c | 12 +-
> fs/xfs/xfs_super.h | 1 +
> include/linux/dax.h | 56 ++++-
> include/linux/fs.h | 12 +-
> include/linux/memremap.h | 12 ++
> include/linux/mm.h | 2 +
> include/linux/page-flags.h | 6 +
> mm/memory-failure.c | 257 ++++++++++++++++-------
> 26 files changed, 1087 insertions(+), 182 deletions(-)
> create mode 100644 fs/xfs/xfs_notify_failure.c
>
> --
> 2.35.1
>
>
>
next prev parent reply other threads:[~2022-05-11 0:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 14:36 Shiyang Ruan
2022-05-08 14:36 ` [PATCH v14 01/07] dax: Introduce holder for dax_device Shiyang Ruan
2022-05-08 14:36 ` [PATCH v14 02/07] mm: factor helpers for memory_failure_dev_pagemap Shiyang Ruan
2022-05-08 14:36 ` [PATCH v14 03/07] pagemap,pmem: Introduce ->memory_failure() Shiyang Ruan
2022-05-08 14:36 ` [PATCH v14 04/07] fsdax: Introduce dax_lock_mapping_entry() Shiyang Ruan
2022-05-08 14:36 ` [PATCH v14 05/07] mm: Introduce mf_dax_kill_procs() for fsdax case Shiyang Ruan
2022-05-08 14:36 ` [PATCH v14 06/07] xfs: Implement ->notify_failure() for XFS Shiyang Ruan
2022-05-08 14:36 ` [PATCH v14 07/07] fsdax: set a CoW flag when associate reflink mappings Shiyang Ruan
2022-05-08 14:36 ` [PATCH v11 01/07] fsdax: Output address in dax_iomap_pfn() and rename it Shiyang Ruan
2022-05-08 14:36 ` [PATCH v11 02/07] fsdax: Introduce dax_iomap_cow_copy() Shiyang Ruan
2022-05-08 14:36 ` [PATCH v11 03/07] fsdax: Replace mmap entry in case of CoW Shiyang Ruan
2022-05-08 14:36 ` [PATCH v11 04/07] fsdax: Add dax_iomap_cow_copy() for dax zero Shiyang Ruan
2022-05-08 14:36 ` [PATCH v11 05/07] fsdax: Dedup file range to use a compare function Shiyang Ruan
2022-05-08 14:36 ` [PATCH v11 06/07] xfs: support CoW in fsdax mode Shiyang Ruan
2022-05-10 5:45 ` Christoph Hellwig
2022-05-10 10:06 ` Shiyang Ruan
2022-05-11 2:25 ` [PATCH v11.1 " Shiyang Ruan
2022-05-08 14:36 ` [PATCH v11 07/07] xfs: Add dax dedupe support Shiyang Ruan
2022-05-10 9:32 ` [PATCHSETS] v14 fsdax-rmap + v11 fsdax-reflink Christoph Hellwig
2022-05-11 0:03 ` Darrick J. Wong [this message]
2022-05-11 1:48 ` Dave Chinner
2022-05-11 1:55 ` Dan Williams
2022-05-11 2:19 ` Dave Chinner
2022-05-11 2:28 ` Andrew Morton
2022-05-11 2:43 ` Darrick J. Wong
2022-05-11 5:24 ` Andrew Morton
2022-05-11 6:21 ` Dave Chinner
2022-05-11 15:19 ` Darrick J. Wong
2022-05-11 15:46 ` Dan Williams
2022-05-12 12:27 ` Shiyang Ruan
2022-06-02 9:42 ` Shiyang Ruan
2022-06-02 17:18 ` Darrick J. Wong
2022-06-02 17:47 ` Andrew Morton
2022-05-11 4:20 ` Dan Williams
2022-05-11 4:34 ` Darrick J. Wong
2022-06-02 18:56 ` Andrew Morton
2022-06-03 1:07 ` Shiyang Ruan
2022-06-03 1:36 ` Shiyang Ruan
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=20220511000352.GY27195@magnolia \
--to=djwong@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jane.chu@oracle.com \
--cc=linmiaohe@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=naoya.horiguchi@nec.com \
--cc=nvdimm@lists.linux.dev \
--cc=rgoldwyn@suse.de \
--cc=ruansy.fnst@fujitsu.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox