Re: how does meta xlator work?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Anand Avati <avati@xxxxxxxxxxx> wrote:

> If FUSE implements proper direct_io semantics (somewhat like how O_DIRECT
> flag is handled) and allows the mode to be enabled by the FS in open_cbk,
> then I guess such a special handling of 0-byte need not be necessary?

Yes, this is how it should be done.

While there I see there is a FUSE_FOPEN_KEEP_CACHE  and
FUSE_FOPEN_NONSEEKABLE. I assume the later means seek should return an
error (which one?), but what does the first one do?

There is no real documentation about this aside from Linux kernel
sources...

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@xxxxxxxxxx
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux