Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1423990
| From | Miklos Szeredi <miklos@szeredi.hu> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] FUSE: Improve aio directIO write performance for size extending writes. |
| Date | 2016-06-16 14:10 +0200 |
| Message-ID | <rKEhr-8cw-7@gated-at.bofh.it> (permalink) |
| References | <rlgBJ-3br-29@gated-at.bofh.it> <rKDEK-7Kx-37@gated-at.bofh.it> <rKE7M-7Uc-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Jun 16, 2016 at 1:51 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote: > On Thu, Jun 16, 2016 at 1:25 PM, Miklos Szeredi <miklos@szeredi.hu> wrote: >> On Thu, Apr 7, 2016 at 1:48 PM, Ashish Sangwan <ashishsangwan2@gmail.com> wrote: >>> While sending the blocking directIO in fuse, the write request is broken >>> into sub-requests, each of default size 128k and all the requests are sent >>> in non-blocking background mode if async_dio mode is supported by libfuse. >>> The process which issue the write wait for the completion of all the >>> sub-requests. Sending multiple requests parallely gives a chance to perform >>> parallel writes in the user space fuse implementation if it is >>> multi-threaded and hence improves the performance. >>> >>> When there is a size extending aio dio write, we switch to >>> blocking mode so that we can properly update the size of the file after >>> completion of the writes. However, in this situation all the sub-requests >>> are sent in serialized manner where the next request is sent only after >>> receiving the reply of the current request. Hence the multi-threaded user >>> space implementation is not utilized properly. >>> >>> This patch changes the size extending aio dio behavior to exactly follow >>> blocking dio. For multi threaded fuse implementation having 10 threads and >>> using buffer size of 64MB to perform async directIO, we are getting double >>> the speed. >>> >>> Signed-off-by: Ashish Sangwan <ashishsangwan2@gmail.com> >> >> Thanks for you patience. Pushed to >> >> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-next >> >> I simplified the logic, please verify that I didn't mess something up. >> > > Hi, > > I would like to test fuse-next on Ubuntu/precise aka 12.04-LTS AMD64. > > Do I need a modern version of libfuse? > Libfuse v2.8.6 is installed here. Fuse will work fine but AFAICS the "async_dio" option was not added to a 2.X release (it could be backported quite simply if needed). Thanks, Miklos
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH] FUSE: Improve aio directIO write performance for size extending writes. Miklos Szeredi <miklos@szeredi.hu> - 2016-06-16 13:30 +0200
Re: [PATCH] FUSE: Improve aio directIO write performance for size extending writes. Sedat Dilek <sedat.dilek@gmail.com> - 2016-06-16 14:00 +0200
Re: [PATCH] FUSE: Improve aio directIO write performance for size extending writes. Miklos Szeredi <miklos@szeredi.hu> - 2016-06-16 14:10 +0200
Re: [PATCH] FUSE: Improve aio directIO write performance for size extending writes. Sedat Dilek <sedat.dilek@gmail.com> - 2016-06-16 14:30 +0200
Re: [PATCH] FUSE: Improve aio directIO write performance for size extending writes. Miklos Szeredi <miklos@szeredi.hu> - 2016-06-16 14:40 +0200
Re: [PATCH] FUSE: Improve aio directIO write performance for size extending writes. Sedat Dilek <sedat.dilek@gmail.com> - 2016-06-20 11:30 +0200
Re: [PATCH] FUSE: Improve aio directIO write performance for size extending writes. Ashish Sangwan <ashishsangwan2@gmail.com> - 2016-06-20 09:00 +0200
csiph-web