Date: Wed, 31 Jan 2018 14:19:51 -0600 From: Mahmoud Al-Qudsi <mqudsi@neosmart.net> To: "Mikhail T." <mi+b@aldan.algebra.com> Cc: freebsd-fs@freebsd.org Subject: Re: Need help with sysutils/fusefs-smbnetfs Message-ID: <CACcTrKcWgkaBCp6Dn64ANtvLGh2kXsAGQHmJkarWjzMh4oUW8w@mail.gmail.com> In-Reply-To: <8868a37f-90ad-a271-2295-bf67164fad19@aldan.algebra.com> References: <8868a37f-90ad-a271-2295-bf67164fad19@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 31, 2018 at 12:31 PM, Mikhail T. <mi+b@aldan.algebra.com> wrote: > The upstream developer primarily works with Linux -- and is not very > responsive at any rate. Can any of the FreeBSD's FUSE-developers take a look > at the port -- the codebase is not very large -- and suggest any > optimizations? How does the performance vary with changes to samba_max_rw_block_size? I only took a cursory glance at the upstream code (ugh, sourceforge) but it acquires a mutex to lock the samba context for each loop in read/write. I could be wrong (never worked with smb code before!) but from what I can see in the `get_ctx` function, it doesn't seem that the context needs to be shared at all: it looks like a new context can instead be obtained for each transfer, (not chunk) eliminating the need to lock and unlock repeatedly in a loop. Mahmoud Al-Qudsi NeoSmart Technologies
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACcTrKcWgkaBCp6Dn64ANtvLGh2kXsAGQHmJkarWjzMh4oUW8w>