On Wed, 7 Jan 2026 09:33:19 -0600 John Groves <[email protected]> wrote:
> Add FUSE_FAMFS_DAX config parameter, to control compilation of famfs > within fuse. > > Signed-off-by: John Groves <[email protected]> A separate commit for this doesn't obviously add anything over combining it with first place the CONFIG_xxx is used. Maybe it's a convention for fs/fuse though. If it is ignore me. > --- > fs/fuse/Kconfig | 14 ++++++++++++++ > 1 file changed, 14 insertions(+) > > diff --git a/fs/fuse/Kconfig b/fs/fuse/Kconfig > index 3a4ae632c94a..3b6d3121fe40 100644 > --- a/fs/fuse/Kconfig > +++ b/fs/fuse/Kconfig > @@ -76,3 +76,17 @@ config FUSE_IO_URING > > If you want to allow fuse server/client communication through > io-uring, > answer Y > + > +config FUSE_FAMFS_DAX > + bool "FUSE support for fs-dax filesystems backed by devdax" > + depends on FUSE_FS > + depends on DEV_DAX > + default FUSE_FS > + select DEV_DAX_FS > + help > + This enables the fabric-attached memory file system (famfs), > + which enables formatting devdax memory as a file system. Famfs > + is primarily intended for scale-out shared access to > + disaggregated memory. > + > + To enable famfs or other fuse/fs-dax file systems, answer Y
