Re: [Avf-fuse-dev] Bug in FUSE 1.1?

[Steve M. <smc...@so...>]

On Tue, Mar 16, 2004 at 03:35:32PM +0100, Miklos Szeredi wrote:
>
>> My only problem is that I'm never seeing large reads at all. I'm
>> mounting with the FUSE_LARGE_READ flag set, but I only ever see 4KB
>> reads in my userland program. I can see that fuse_file_read() in
>> kernel/file.c looks for fc->flags & FUSE_LARGE_READ, but I never see
>> this flag get set. Is this a known issue?
>
>It works for me fine.  Doing a 'cat /mnt/fuse/tmp/t' after mounting
>the fusexmp filesystem yields the following:
>
>bcica:~/avfs/fuse> example/fusexmp /mnt/fuse/ -d -- -l
>unique: 2, opcode: LOOKUP (1), ino: 1, insize: 24
>LOOKUP /tmp
>   INO: 2
>   unique: 2, error: 0 (Success), outsize: 88
>unique: 3, opcode: LOOKUP (1), ino: 2, insize: 22
>LOOKUP /tmp/t
>   INO: 3
>   unique: 3, error: 0 (Success), outsize: 88
>unique: 4, opcode: OPEN (14), ino: 3, insize: 24
>   unique: 4, error: 0 (Success), outsize: 8
>unique: 5, opcode: READ (15), ino: 3, insize: 32
>READ 65536 bytes from 0
>   READ 6 bytes
>   unique: 5, error: 0 (Success), outsize: 14
>unique: 0, opcode: RELEASE (18), ino: 3, insize: 24
>FORGET 1/0
>
>Do you get 4k reads in this case?

No, I see 64K. Sorry for that - looks like a bug in my code in
userland instead then...

Checking, ah: I see it. I'm passing in FUSE_LARGE_READ as part of the
flags to fuse_new. I need to setup a fusermount_args struct instead.

Thanks for the quick response.

-- 
Steve McIntyre, Plasmon                         smc...@so...
Support the Campaign for Audiovisual Free Expression: http://www.eff.org/cafe/