History log of /src/lib/libperfuse/fuse.h |
Revision | | Date | Author | Comments |
1.8 |
| 17-Sep-2021 |
andvar | some love to double letters (in comments).
|
1.7 |
| 18-Oct-2016 |
christos | make this compile again, and simplify.
|
1.6 |
| 31-Oct-2014 |
manu | branches: 1.6.2; FUSE fallocate support There seems to be no fdiscard FUSE operation at the moment, hence that one is left unused.
|
1.5 |
| 28-Dec-2011 |
manu | branches: 1.5.18; Add a FUSE trace facility, with statistics collection. This should help tracking bugs and performance issues
|
1.4 |
| 28-Jun-2011 |
manu | branches: 1.4.2; Add support for extended attributes
|
1.3 |
| 11-May-2011 |
jakllsch | Use sysconf(_SC_PAGESIZE) instead of PAGE_SIZE.
|
1.2 |
| 15-Sep-2010 |
manu | - Use SOCK_DGRAM instead of SOCK_STREAM, as the filesystem seems to assume datagram semantics: when using SOCK_STREAM, if perfused sends frames faster than the filesystem consumes them, it will grab multiple frames at once and discard anything beyond the first one. For now the code can work both with SOCK_DGRAM and SOCK_STREAM, but SOCK_STREAM support will probably have to be removed for the sake of readability.
- Remeber to sync parent directories when moving a node
- In debug output, display the requeue type (readdir, write, etc...)
|
1.1 |
| 25-Aug-2010 |
manu | libperfuse(3) is a PUFFS relay to FUSE. In order to use it, FUSE filesystem must be patched to #include <perfuse.h> in the source files that open /dev/fuse and perform the mount(2) system call. The FUSE filesystem must be linked with -lperfuse.
libperfuse(3) implements the FUSE kernel interface, on which libfuse or any FUSE filesystem that opens /dev/fuse directly can be used.
For now, an external daemon called perfused(8) is used. This may change in the future.
|
1.4.2.1 |
| 17-Apr-2012 |
yamt | sync with head
|
1.5.18.2 |
| 01-Nov-2016 |
snj | Pull up following revision(s) (requested by manu in ticket #1266): lib/libperfuse/fuse.h: revision 1.7 lib/libperfuse/libperfuse.3: revision 1.4, 1.5 lib/libperfuse/perfuse.c: revision 1.38-1.40 lib/libperfuse/perfuse_if.h: revision 1.21, 1.22 usr.sbin/perfused/msg.c: revision 1.23, 1.24 usr.sbin/perfused/perfused.8: revision 1.12 Make FUSE socket buffer tunable When dealing with high I/O throughput, we could run out of buffer space if the filesystem was not consuming requests fast enough. Here we slightly raise the buffer size, and we make it tunable through the PERFUSE_BUFSIZE environment variable so that we can cope with higher requirement later. While there, document PERFUSE_OPTIONS environment variable. -- make this compile again, and simplify. -- Sort sections. new sentence, new line. Whitespace. -- make the env stuff visible. -- remove dup function
|
1.5.18.1 |
| 05-Nov-2014 |
snj | branches: 1.5.18.1.4; Pull up following revision(s) (requested by manu in ticket #181): lib/libperfuse/fuse.h: revision 1.6 lib/libperfuse/ops.c: revision 1.78 lib/libperfuse/perfuse.c: revision 1.35 lib/libperfuse/perfuse_priv.h: revision 1.36 lib/libpuffs/dispatcher.c: revision 1.48 lib/libpuffs/opdump.c: revision 1.37 lib/libpuffs/puffs.c: revision 1.118 lib/libpuffs/puffs.h: revision 1.126 lib/libpuffs/puffs_ops.3: revisions 1.40-1.41 sys/fs/puffs/puffs_msgif.h: revision 1.82-1.83 sys/fs/puffs/puffs_msgif.h: revision 1.82 sys/fs/puffs/puffs_vnops.c: revision 1.196 Add PUFFS support for fallocate and fdiscard operations -- libpuffs support for fallocate and fdiscard operations -- Add PUFFS_HAVE_FALLOCATE in puffs_msgif.h so that filesystem can decide at build time wether fallocate is usable -- FUSE fallocate support There seems to be no fdiscard FUSE operation at the moment, hence that one is left unused.
|
1.5.18.1.4.1 |
| 18-Jan-2017 |
skrll | Sync with netbsd-5
|
1.6.2.1 |
| 04-Nov-2016 |
pgoyette | Sync with HEAD
|