On 07/05/2012 05:07 PM, Nikolaus Rath wrote: > Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@xxxxxxxxxxxxxxxx> writes: >>> While I try to get this to compile, >> >> That's good news! Thanks a lot! The fuse and fsdevel mainling lists were corrupted in you original message, so looping the lists back in. > Ok, I got it to compile and tested it by copying a large file into an > S3QL FUSE file system using different block sizes. At first glance, > things look fantastic. That's good news actually! :) > With kernel 3.2: > > Blocksize: 4k > 131072000 bytes (131 MB) copied, 7.76037 s, 16.9 MB/s > [snip] > > However, I suspect that most of the gain is really because with the > patch most of the data is still in the kernel cache when dd finishes and > hasn't yet been received by the FUSE client. > > > Is there a way to force flushing of the fuse cache, so that I can > measure the time for dd + final flush? Actually when dd closes an output file the whole page cache which relates to it gets flushed to the userspace! This is due to how FUSE write requests are served. That said -- you've already measured writeback with flush :) > > Best, > > -Nikolaus > -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
