linux-sg2042/fs/fuse
Miklos Szeredi 0e9663ee45 fuse: add blksize field to fuse_attr
There are cases when the filesystem will be passed the buffer from a single
read or write call, namely:

 1) in 'direct-io' mode (not O_DIRECT), read/write requests don't go
    through the page cache, but go directly to the userspace fs

 2) currently buffered writes are done with single page requests, but
    if Nick's ->perform_write() patch goes it, it will be possible to
    do larger write requests.  But only if the original write() was
    also bigger than a page.

In these cases the filesystem might want to give a hint to the app
about the optimal I/O size.

Allow the userspace filesystem to supply a blksize value to be returned by
stat() and friends.  If the field is zero, it defaults to the old
PAGE_CACHE_SIZE value.

Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-10-18 14:37:31 -07:00
..
Makefile [PATCH] fuse: add control filesystem 2006-06-25 10:01:19 -07:00
control.c [PATCH] mark struct inode_operations const 1 2007-02-12 09:48:46 -08:00
dev.c fuse: no ENOENT from fuse device read 2007-10-17 08:43:04 -07:00
dir.c fuse: add blksize field to fuse_attr 2007-10-18 14:37:31 -07:00
file.c fuse: add support for mandatory locking 2007-10-18 14:37:31 -07:00
fuse_i.h fuse: add support for mandatory locking 2007-10-18 14:37:31 -07:00
inode.c fuse: add blksize field to fuse_attr 2007-10-18 14:37:31 -07:00