[kio] [Bug 291835] KIO very slow when copying from network through fish

Mark markg85 at gmail.com
Wed Mar 26 13:30:34 GMT 2014


https://bugs.kde.org/show_bug.cgi?id=291835

--- Comment #25 from Mark <markg85 at gmail.com> ---
Ohh, this changes things a bit.

Quote: "If CAP_LARGE_READX  or CAP_LARGE_WRITEX  capability is enabled on the
SMB Negotiate Server Response,   the maximum buffer size  used  is  61440 (60K)
 for large read( SMB_COM_ READ_ANDX )  and 65535 (64K) for large write
(SMB_COM_WRITE_ANDX) , regardless of MaxBufferSize.   But this is only true if
the SMB signing is not turned on (we will discuss this further in the next
section). "

On windows they default to enable CAP_LARGE_READX and CAP_LARGE_WRITEX. They
also default to disable server signing. Samba defaults to large readwrite to
true and server signing to disabled as can be read here:
http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html

Thus the MAX_XFER_BUF_SIZE in KIO should be set to 65535 if i'm reading the
documentation correctly.

However, since this value is dependent on memory and samba server settings,
that means it has to have a bit of logic in it to determine the correct value
(just a define won't do). In other terms: there is some work to do there in
getting it working how it should be working according to the defaults.

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list