Kconfig 2.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. config FUSE_FS
  3. tristate "FUSE (Filesystem in Userspace) support"
  4. select FS_POSIX_ACL
  5. select FS_IOMAP
  6. help
  7. With FUSE it is possible to implement a fully functional filesystem
  8. in a userspace program.
  9. There's also a companion library: libfuse2. This library is available
  10. from the FUSE homepage:
  11. <https://github.com/libfuse/>
  12. although chances are your distribution already has that library
  13. installed if you've installed the "fuse" package itself.
  14. See <file:Documentation/filesystems/fuse/fuse.rst> for more information.
  15. See <file:Documentation/Changes> for needed library/utility version.
  16. If you want to develop a userspace FS, or if you want to use
  17. a filesystem based on FUSE, answer Y or M.
  18. config CUSE
  19. tristate "Character device in Userspace support"
  20. depends on FUSE_FS
  21. help
  22. This FUSE extension allows character devices to be
  23. implemented in userspace.
  24. If you want to develop or use a userspace character device
  25. based on CUSE, answer Y or M.
  26. config VIRTIO_FS
  27. tristate "Virtio Filesystem"
  28. depends on FUSE_FS
  29. select VIRTIO
  30. help
  31. The Virtio Filesystem allows guests to mount file systems from the
  32. host.
  33. If you want to share files between guests or with the host, answer Y
  34. or M.
  35. config FUSE_DAX
  36. bool "Virtio Filesystem Direct Host Memory Access support"
  37. default y
  38. select INTERVAL_TREE
  39. depends on VIRTIO_FS
  40. depends on FS_DAX
  41. depends on DAX
  42. help
  43. This allows bypassing guest page cache and allows mapping host page
  44. cache directly in guest address space.
  45. If you want to allow mounting a Virtio Filesystem with the "dax"
  46. option, answer Y.
  47. config FUSE_PASSTHROUGH
  48. bool "FUSE passthrough operations support"
  49. default y
  50. depends on FUSE_FS
  51. select FS_STACK
  52. help
  53. This allows bypassing FUSE server by mapping specific FUSE operations
  54. to be performed directly on a backing file.
  55. If you want to allow passthrough operations, answer Y.
  56. config FUSE_IO_URING
  57. bool "FUSE communication over io-uring"
  58. default y
  59. depends on FUSE_FS
  60. depends on IO_URING
  61. help
  62. This allows sending FUSE requests over the io-uring interface and
  63. also adds request core affinity.
  64. If you want to allow fuse server/client communication through io-uring,
  65. answer Y