On Fri, Jul 6, 2012 at 2:53 AM, Liu Yuan <namei.unix@xxxxxxxxx> wrote: > On 07/05/2012 06:50 PM, Mitsuo Hayasaka wrote: >> One of the ways to solve this is to make them tunable. >> In this series, the new sysfs parameter max_pages_per_req is introduced. >> It limits the maximum read/write size in fuse request and it can be >> changed from 32 to 256 pages in current implementations. When the >> max_read/max_write mount option is specified, FUSE request size is set >> per mount. (The size is rounded-up to page size and limited up to >> max_pages_per_req.) > > Why maxim 256 pages? If we are here, we can go further: most of object > storage system has object size of multiple to dozens of megabytes. So I > think probably 1M is too small. Our distribution storage system has 4M > per object, so I think at least maxim size could be bigger than 4M. The maximum pipe size on my system is 1M, so if you go beyond that, splicing from the FD won't work. Also, the userspace client must reserve a buffer this size so it can receive a write, which is a waste since most requests are much smaller. -- Han-Wen Nienhuys - hanwen@xxxxxxxxx - http://www.xs4all.nl/~hanwen -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
