Searched hist:"7678 ac50615d9c7a491d9861e020e4f5f71b594c" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/fs/fuse/ |
| H A D | fuse_i.h | diff 7678ac50615d9c7a491d9861e020e4f5f71b594c Tue Nov 05 09:05:52 CST 2013 Andrew Gallagher <agallagher@fb.com> fuse: support clients that don't implement 'open'
open/release operations require userspace transitions to keep track
of the open count and to perform any FS-specific setup. However,
for some purely read-only FSs which don't need to perform any setup
at open/release time, we can avoid the performance overhead of
calling into userspace for open/release calls.
This patch adds the necessary support to the fuse kernel modules to prevent
open/release operations from hitting in userspace. When the client returns
ENOSYS, we avoid sending the subsequent release to userspace, and also
remember this so that future opens also don't trigger a userspace
operation.
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
|
| H A D | file.c | diff 7678ac50615d9c7a491d9861e020e4f5f71b594c Tue Nov 05 09:05:52 CST 2013 Andrew Gallagher <agallagher@fb.com> fuse: support clients that don't implement 'open'
open/release operations require userspace transitions to keep track
of the open count and to perform any FS-specific setup. However,
for some purely read-only FSs which don't need to perform any setup
at open/release time, we can avoid the performance overhead of
calling into userspace for open/release calls.
This patch adds the necessary support to the fuse kernel modules to prevent
open/release operations from hitting in userspace. When the client returns
ENOSYS, we avoid sending the subsequent release to userspace, and also
remember this so that future opens also don't trigger a userspace
operation.
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
|