All of lore.kernel.org
 help / color / mirror / Atom feed
From: HAYASAKA Mitsuo <mitsuo.hayasaka.hu@hitachi.com>
To: Nikolaus Rath <Nikolaus@rath.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	fuse-devel@lists.sourceforge.net, linux-kernel@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 19:09:15 +0900	[thread overview]
Message-ID: <4FF6B94B.60204@hitachi.com> (raw)
In-Reply-To: <87vci2gxzr.fsf@inspiron.ap.columbia.edu>

Hi Nikolaus,

Thank you for your comments.

(2012/07/05 22:04), Nikolaus Rath wrote:
> Mitsuo Hayasaka<mitsuo.hayasaka.hu@hitachi.com>  writes:
>> Hi,
>>
>> This patch series make maximum read/write request size tunable in FUSE.
>> Currently, it is limited to FUSE_MAX_PAGES_PER_REQ which is equal
>> to 32 pages. It is required to change it in order to improve the
>> throughput since optimized value depends on various factors such
>> as type and version of local filesystems used and HW specs, etc.
>
> This truly is a joyful week for FUSE :-).
>
> Are these patches compatible with the fuse write-back patch series
> posted by Pavel a few days ago?


I applied this patch series to the latest upstream kernel and measured
the read/write throughput using it. So, I have not try Pavel's patch yet.

However, I think it is compatible with his write-back patch series
since it just makes maximum limit of fuse request size tunable.
And my patch will be effective even for direct I/O.

Thanks,

>
>
> Thanks,
>
>     -Nikolaus
>


  reply	other threads:[~2012-07-06 10:09 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 [this message]
2012-07-06  5:53 ` Liu Yuan
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=4FF6B94B.60204@hitachi.com \
    --to=mitsuo.hayasaka.hu@hitachi.com \
    --cc=Nikolaus@rath.org \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --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.