https://bugs.kde.org/show_bug.cgi?id=291835
CnZhx changed:
What|Removed |Added
CC|z...@cnzhx.net |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=291835
aux...@gmail.com changed:
What|Removed |Added
CC||aux...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=291835
Harald Sitter changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/kio
https://bugs.kde.org/show_bug.cgi?id=291835
Harald Sitter changed:
What|Removed |Added
Status|CONFIRMED |ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=291835
--- Comment #60 from Fabby ---
Holy Moly! round(106/108*100)=98% efficiency and (nearly) 100% speed increase!
Where can I send the bottle of Champagne? (or crate of Belgian beer if that's
your preference...)
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=291835
--- Comment #59 from Christoph Feck ---
Does "dynamic request size" mean that it starts e.g. at 256KB, then measures
the time it needed, and if it was less than 1 second, then it will double the
buffer size, measure again, etc. up to (say) 128MB?
--
https://bugs.kde.org/show_bug.cgi?id=291835
--- Comment #58 from Nate Graham ---
Fantastic work, Harald! Really top-notch engineering right there.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=291835
Harald Sitter changed:
What|Removed |Added
CC||sit...@kde.org
--- Comment #57 from Harald
https://bugs.kde.org/show_bug.cgi?id=291835
Nate Graham changed:
What|Removed |Added
CC||fabrizio.mar...@gmail.com
--- Comment #56 from
https://bugs.kde.org/show_bug.cgi?id=291835
Nate Graham changed:
What|Removed |Added
Severity|normal |major
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=291835
Nate Graham changed:
What|Removed |Added
CC||avaman...@gmail.com
--- Comment #55 from Nate
https://bugs.kde.org/show_bug.cgi?id=291835
Alexander Potashev changed:
What|Removed |Added
CC||aspotas...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=291835
Mark changed:
What|Removed |Added
CC|mark...@gmail.com |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=291835
CnZhx changed:
What|Removed |Added
CC||z...@cnzhx.net
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=291835
Patrick Silva changed:
What|Removed |Added
CC||bugsefor...@gmx.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=291835
pos...@posteo.eu changed:
What|Removed |Added
CC||pos...@posteo.eu
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=291835
Scott Deagan changed:
What|Removed |Added
CC||scott.dea...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=291835
Nate Graham changed:
What|Removed |Added
Component|default |Samba
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=291835
--- Comment #54 from Mark ---
(In reply to Christoph Feck from comment #52)
> Mark, the issue is not whether user-space code can saturate the network. The
> problem is that there is no async I/O API available in libsmbclient.
>
> If
https://bugs.kde.org/show_bug.cgi?id=291835
--- Comment #53 from Krzysztof Marczak ---
Maybe look for the answers in other software. Gnome-commander also uses SMB and
SFTP and uses all possible hardware throughput. Maybe if you look into source
code of this application,
https://bugs.kde.org/show_bug.cgi?id=291835
--- Comment #52 from Christoph Feck ---
Mark, the issue is not whether user-space code can saturate the network. The
problem is that there is no async I/O API available in libsmbclient.
If I understand the previous comments correctly,
https://bugs.kde.org/show_bug.cgi?id=291835
--- Comment #51 from Mark ---
FWIW in my mind this is by no means a user space vs kernel space thing.
I talked about sendfile/splice before in this very bug, back then i had no
numbers to back that up.
Now i do. Here's what i did.
https://bugs.kde.org/show_bug.cgi?id=291835
--- Comment #50 from Christoph Feck ---
Actually, what that bug proposes is the reverse of what we need here: We would
like kio-smb to use a kernel mount to speed up all KDE applications that use
KIO.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=291835
--- Comment #49 from Nate Graham ---
> The only way to get the speed is to use the Linux kernel CIFS VFS, which
> isn't available via API, only via a mount.
Which we could do via https://bugs.kde.org/show_bug.cgi?id=75324
--
You are
https://bugs.kde.org/show_bug.cgi?id=291835
--- Comment #48 from Christoph Feck ---
libsmclient does not offer an async I/O API. The only way to get the speed is
to use the Linux kernel CIFS VFS, which isn't available via API, only via a
mount.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=291835
hrvo...@jankovci.net changed:
What|Removed |Added
CC||hrvo...@jankovci.net
--
You are
https://bugs.kde.org/show_bug.cgi?id=291835
Nate Graham changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=291835
--- Comment #47 from oli...@openbrackets.net ---
@Nate Graham
Yes, those were my pragmatic conclusions too.
I think the buffer tunable is possible, but it's a cludge.
The real issue is network latency and the fact that
https://bugs.kde.org/show_bug.cgi?id=291835
Nate Graham changed:
What|Removed |Added
URL|
https://bugs.kde.org/show_bug.cgi?id=291835
Nate Graham changed:
What|Removed |Added
Version|4.11.1 |unspecified
30 matches
Mail list logo