Mitsuo Hayasaka <mitsuo.hayasaka.hu@xxxxxxxxxxx> writes: > Add a max_pages_per_req sysfs paramater to limit the maximum > read/write request size. It can be changed to arbitrary number > between 32 and the nr_pages equivalent to pipe_max_size, and the > 32 pages are set by default. > > The sysfs parameter control is required, as follows. > > * The libfuse should change the current MIN_BUFSIZE limitation > according to the current maximum request size in FUSE. If not, > the libfuse must always set MIN_BUFSIZE to the maximum request > limit (= [nr_pages (equivalent to pipe_max_size) * 4KB + 0x1000]), > which leads to waste of memory. I don't see the purpose of this sysfs parameter. Userspace can calculate the needed buffer size from the max_read/max_write parameters, can't it? > > * It is easy to find and set the paramter to the optimized value > in order to improve the read/write throughput, since the > maximum request limit does not always provides the highest > throughput. So basically this is a global max_read/max_write limit? For that a better solution would be to add it to /etc/fuse.conf. But I have doubts about whether this is useful. Thanks, Miklos -- 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
