https://bugs.kde.org/show_bug.cgi?id=346619
--- Comment #4 from Vladimir <vladimir.mensha...@gmail.com> --- (In reply to Nate Graham from comment #3) > Thanks for the update! So the slowness of not respecting f_bsize manifested > when you used Dolphin to move or copy a file (via copy-paste or > drag-and-drop) to a local mount for an MTP device? Yes, it was like that. Current value 128K is enough for everyone © Almost I think it's generally good practive to align IO size to size of filesystem block, so filesystem will not squeeze your data into any tail-space in case of small write, etc. My MTP implementation uses partial reads/writes to avoid full object sending/retrieval, making MTP as fast as any other way to transfer data from/to device. The problem with partial objects, it's done from userspace on android, and this approach has an additional overhead of starting/committing object transaction. I've decided to advertise large block size to userspace, it worked with some other file managers, but not the dolphin. :) Thanks -- You are receiving this mail because: You are watching all bug changes.
