| Summary: | MTP IOSlave should use f_bsize for block size | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | Vladimir <vladimir.menshakov> |
| Component: | general | Assignee: | David Faure <faure> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | wishlist | CC: | kdelibs-bugs, nate, postix |
| Priority: | NOR | ||
| Version: | 5.47.0 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Vladimir
2015-04-25 07:25:33 UTC
Is this still an issue with KDE Frameworks 5.47 and Dolphin 18.04.x? (In reply to Nate Graham from comment #1) > Is this still an issue with KDE Frameworks 5.47 and Dolphin 18.04.x? Soft of. This problem has been leveraged by increasing IO size in recent versions, it's 128K now. But it's still not taking f_frsize/f_bsize into account. 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? (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 Thanks for the info! As soon as I figure out where this setting is located, I'll submit a patch. If you know where I can find it, please don't be shy! :) Nate, the f_bsize setting can be found via http://man7.org/linux/man-pages/man3/statvfs.3.html But I am not sure if KIO should look at it. My filesystem block size reports 4K, so general file copying would get slower respecting it compared to the 128K value we use now. If the default value is good enough now, and respecting the system's value might be worse, maybe we should close this? > If the default value is good enough now, and respecting the system's value might be worse, maybe we should close this?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |