Behaviour of system tray bandwidth indicator
Reindl Harald
h.reindl at thelounge.net
Thu Mar 20 16:32:37 UTC 2014
Am 20.03.2014 17:30, schrieb Patrick O'Callaghan:
> On Thu, 2014-03-20 at 11:54 +0100, Kevin Kofler wrote:
>> The UI can only indicate what is visible to user space, it has no way to,
>> nor is it expected to, know what the kernel does behind the scenes. If the
>> kernel reports that it has processed the data, the UI shows it as processed.
>> That is exactly as designed.
>
> Presumably 'cp' doesn't know what the kernel does behind the scenes
> either, so I did a further experiment (using a 2.2GB test file):
>
> 1) NFS server mounted async:
>
> $ time cp TestFile /storage/public/Media
>
> real 4m4.959s
> user 0m0.011s
> sys 0m1.456s
>
> 2) NFS server mounted sync:
>
> $ time cp TestFile /storage/public/Media
>
> real 5m41.806s
> user 0m0.113s
> sys 0m8.609s
>
> Clearly there is a difference in real time and system time which we can
> put down to kernel buffering. However the difference is nothing like as
> great as that shown by the notification widget under KDE, in which the
> async case shows no transfer bandwidth bring consumed after a couple of
> seconds, even though it still takes just as long to complete. In what
> way is the Dolphin transfer different from cp?
cp does not show any progress bar
most likely because the coerutils-developers decided
against because the reason of that thread
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/kde/attachments/20140320/be9ed6f3/attachment.sig>
More information about the kde
mailing list