On Sat, Aug 4, 2018, 11:56 PM Conrad Meyer wrote:
> On Sat, Aug 4, 2018 at 3:54 PM, Conrad Meyer wrote:
> > It was chosen arbitrarily. Either is a big improvement over 4k.
> >
> > According to the bug reporter, 64k is a common choice in other
> > implementations. But I have no objection to MAX
On Sat, Aug 4, 2018 at 3:54 PM, Conrad Meyer wrote:
> It was chosen arbitrarily. Either is a big improvement over 4k.
>
> According to the bug reporter, 64k is a common choice in other
> implementations. But I have no objection to MAXPHYS.
(It should probably be globally tunable/sysctlable, at
On Sat, Aug 4, 2018 at 3:46 PM, Warner Losh wrote:
> On Thu, Aug 2, 2018 at 1:25 PM, Conrad Meyer wrote:
>>
>> Author: cem
>> Date: Thu Aug 2 19:25:43 2018
>> New Revision: 337165
>> URL: https://svnweb.freebsd.org/changeset/base/337165
>>
>> Log:
>> FUSE: Bump maximum IO size to enable more p
On Thu, Aug 2, 2018 at 1:25 PM, Conrad Meyer wrote:
> Author: cem
> Date: Thu Aug 2 19:25:43 2018
> New Revision: 337165
> URL: https://svnweb.freebsd.org/changeset/base/337165
>
> Log:
> FUSE: Bump maximum IO size to enable more performant operation
>
> Various components restrict size of I
Author: cem
Date: Thu Aug 2 19:25:43 2018
New Revision: 337165
URL: https://svnweb.freebsd.org/changeset/base/337165
Log:
FUSE: Bump maximum IO size to enable more performant operation
Various components restrict size of IO passed up to the userspace filesystem
based on the mount's f_ios
