From: Liu Yuan <namei.unix@gmail.com>
To: Mitsuo Hayasaka <mitsuo.hayasaka.hu@hitachi.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
fuse-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, yrl.pp-manager.tt@hitachi.com
Subject: Re: [RFC PATCH 0/5] fuse: make maximum read/write request size tunable
Date: Fri, 06 Jul 2012 13:53:46 +0800 [thread overview]
Message-ID: <4FF67D6A.8060707@gmail.com> (raw)
In-Reply-To: <20120705105017.17812.95542.stgit@ltc137.sdl.hitachi.co.jp>
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.
Thanks,
Yuan
next prev parent reply other threads:[~2012-07-06 5:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 10:50 [RFC PATCH 0/5] fuse: make maximum read/write request size tunable Mitsuo Hayasaka
2012-07-05 10:50 ` [RFC PATCH 1/5] " Mitsuo Hayasaka
2012-07-05 10:50 ` [RFC PATCH 2/5] fuse: do not create cache for fuse request allocation Mitsuo Hayasaka
2012-07-05 10:51 ` [RFC PATCH 3/5] fuse: make default global limit minimum value Mitsuo Hayasaka
2012-07-05 10:51 ` [RFC PATCH 4/5] fuse: add a sysfs parameter to control maximum request size Mitsuo Hayasaka
2012-07-05 10:51 ` [RFC PATCH 5/5] fuse: add documentation of sysfs parameter to limit maximum fuse " Mitsuo Hayasaka
2012-07-06 12:54 ` Rob Landley
2012-07-12 13:13 ` HAYASAKA Mitsuo
2012-07-05 13:04 ` [RFC PATCH 0/5] fuse: make maximum read/write request size tunable Nikolaus Rath
2012-07-06 10:09 ` HAYASAKA Mitsuo
2012-07-06 5:53 ` Liu Yuan [this message]
2012-07-06 13:58 ` [fuse-devel] " Han-Wen Nienhuys
2012-07-12 5:58 ` HAYASAKA Mitsuo
2012-07-12 6:13 ` Liu Yuan
2012-07-12 10:13 ` Miklos Szeredi
2012-07-13 7:30 ` HAYASAKA Mitsuo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FF67D6A.8060707@gmail.com \
--to=namei.unix@gmail.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mitsuo.hayasaka.hu@hitachi.com \
--cc=yrl.pp-manager.tt@hitachi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.