From: John Groves <john@groves.net>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: fuse-devel@lists.linux.dev, Amir Goldstein <amir73il@gmail.com>,
"Darrick J . Wong" <djwong@kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
nvdimm@lists.linux.dev, linux-cxl@vger.kernel.org
Subject: Re: [PATCH v5 00/10] fuse: DAX device based extent maps (famfs)
Date: Tue, 20 Oct 2026 11:50:45 -0500 [thread overview]
Message-ID: <atebTqE6E7qrEmqI@groves.net> (raw)
In-Reply-To: <20261016151638.2962413-1-mszeredi@redhat.com>
On 26/10/16 05:16PM, Miklos Szeredi wrote:
> This is the FUSIfication of the famfs-fuse patchset.
>
> - extent maps are assigned to a backing ID
>
> - 64 bit backing ID's managed by server
>
> - maps can be linear or cyclic (striped)
>
> - API supports nesting, but not implemented yet (i.e. multiple striped
> extents per inode, a-la famfs)
>
> libfuse/famfs trees for testing:
>
> https://github.com/szmi/libfuse.git#extent-map-v3
> https://github.com/jagalactic/famfs.git#master
>
> This patchset:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git#for-next
>
> Passes famfs smoke test on emulated dax device.
>
> Comments are welcome.
>
> Thanks,
> Miklos
>
> ---
> Changes since v4:
>
> - extent array (John)
> - error out on truncate/hole punch on a dax backed file (Sashiko)
> - small fix (Sashiko)
>
> Changes since v3:
>
> - redid the first patch (prompted by sashiko: passing dev_t is racy)
> - more fixes (John, Amir Sashiko)
>
> Changes since v2:
>
> - add a trivial prep patch modifying drivers/dax/super.c
> - reserve zero value for 64 bit backing ID (Amir)
> - add Originally-by: tag to acknowledge John's work
> - more fixes and cleanups (Amir, Sashiko)
>
> Changes since v1:
>
> - moved 3 prep patches to fuse.git#for-next
> - introduce FUSE_PASSTHROUGH_V2 (Amir)
> - lots of small fixes and cleanups (Amir, Sashiko)
>
> ---
> John Groves (2):
> dax: add fsdev_dax_from_file()
> fuse: resolve extent maps in O(1) when possible
>
> Miklos Szeredi (8):
> dax: use READ_ONCE() in dax_holder()
> fuse: add helpers for EIO return value with kernel message
> fuse: support 64 bit, server allocated backing ID
> fuse: support opening 64 bit backing ID
> fuse: add support for opening dax device as backing
> fuse: add extent map data structure
> fuse: add extent map I/O support
> fuse: add support for striped backing
>
> drivers/dax/fsdev.c | 23 +++
> drivers/dax/super.c | 5 +-
> fs/file.c | 1 +
> fs/fuse/Makefile | 2 +-
> fs/fuse/backing.c | 302 ++++++++++++++++++++++++------
> fs/fuse/dev.c | 54 ++++--
> fs/fuse/dev.h | 3 +
> fs/fuse/dir.c | 6 +-
> fs/fuse/ext_map.c | 376 ++++++++++++++++++++++++++++++++++++++
> fs/fuse/file.c | 33 +++-
> fs/fuse/fuse_i.h | 79 +++++++-
> fs/fuse/inode.c | 25 ++-
> fs/fuse/iomode.c | 116 ++++++------
> fs/fuse/notify.c | 75 ++++++++
> fs/fuse/passthrough.c | 66 +++----
> include/linux/dax.h | 3 +-
> include/uapi/linux/fuse.h | 53 +++++-
> 17 files changed, 1044 insertions(+), 178 deletions(-)
> create mode 100644 fs/fuse/ext_map.c
>
> --
> 2.54.0
>
For the series:
Reviewed-by: John Groves <john@groves.net>
Tested-by: John Groves <john@groves.net>
prev parent reply other threads:[~2026-10-20 16:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 15:16 [PATCH v5 00/10] fuse: DAX device based extent maps (famfs) Miklos Szeredi
2026-10-16 15:16 ` [PATCH v5 01/10] dax: add fsdev_dax_from_file() Miklos Szeredi
2026-10-16 15:20 ` Dave Jiang
2026-10-16 15:28 ` Gregory Price
2026-10-16 15:16 ` [PATCH v5 02/10] dax: use READ_ONCE() in dax_holder() Miklos Szeredi
2026-10-16 15:20 ` Dave Jiang
2026-10-16 15:16 ` [PATCH v5 03/10] fuse: add helpers for EIO return value with kernel message Miklos Szeredi
2026-10-16 15:16 ` [PATCH v5 04/10] fuse: support 64 bit, server allocated backing ID Miklos Szeredi
2026-10-16 15:16 ` [PATCH v5 05/10] fuse: support opening 64 bit " Miklos Szeredi
2026-10-16 15:16 ` [PATCH v5 06/10] fuse: add support for opening dax device as backing Miklos Szeredi
2026-10-16 15:16 ` [PATCH v5 07/10] fuse: add extent map data structure Miklos Szeredi
2026-10-16 15:16 ` [PATCH v5 08/10] fuse: add extent map I/O support Miklos Szeredi
2026-10-16 15:16 ` [PATCH v5 09/10] fuse: add support for striped backing Miklos Szeredi
2026-10-16 15:16 ` [PATCH v5 10/10] fuse: resolve extent maps in O(1) when possible Miklos Szeredi
2026-10-20 16:50 ` John Groves [this message]
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=atebTqE6E7qrEmqI@groves.net \
--to=john@groves.net \
--cc=alison.schofield@intel.com \
--cc=amir73il@gmail.com \
--cc=dave.jiang@intel.com \
--cc=djwong@kernel.org \
--cc=fuse-devel@lists.linux.dev \
--cc=linux-cxl@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.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