linux-kernel - Re: [RFC PATCH 0/5] fuse: make maximum read/write request size tunable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4FF6B94B.60204@hitachi.com>
Date:	Fri, 06 Jul 2012 19:09:15 +0900
From:	HAYASAKA Mitsuo <mitsuo.hayasaka.hu@...achi.com>
To:	Nikolaus Rath <Nikolaus@...h.org>
Cc:	Miklos Szeredi <miklos@...redi.hu>,
	fuse-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	yrl.pp-manager.tt@...achi.com
Subject: Re: [RFC PATCH 0/5] fuse: make maximum read/write request size tunable

Hi Nikolaus,

Thank you for your comments.

(2012/07/05 22:04), Nikolaus Rath wrote:
> Mitsuo Hayasaka<mitsuo.hayasaka.hu@...achi.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
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/