From 6c7d45e4631784d0e077e806521a736da6b0266e Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 7 Apr 2013 18:18:44 +0200 Subject: IRC. --- open_issues/time.mdwn | 75 ++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 74 insertions(+), 1 deletion(-) (limited to 'open_issues/time.mdwn') diff --git a/open_issues/time.mdwn b/open_issues/time.mdwn index ab239aef..cc3951c3 100644 --- a/open_issues/time.mdwn +++ b/open_issues/time.mdwn @@ -1,4 +1,5 @@ -[[!meta copyright="Copyright © 2009, 2011 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2009, 2011, 2013 Free Software Foundation, +Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -67,3 +68,75 @@ While testing some [[performance/IPC_virtual_copy]] performance issues: And I can confirm that with dd if=/dev/zero of=/dev/null bs=4k running, a parallel sleep 10 takes about 20 s (on strauss). + + +# IRC, OFTC, #debian-hurd, 2013-03-30 + + /usr/bin/time seems broken on hurd. It reports weird things. Ex: + # /usr/bin/time sleep 1 + 0.00user 0.00system 4:37:46elapsed 0%CPU (0avgtext+0avgdata + 0maxresident)k + 0inputs+0outputs (0major+0minor)pagefaults 0swaps + o_O + indeed, let's see what that time does + seems like only the elapsed time, %E + not only the time, but also the other variables (pagefaults, cpu + used, etc) are wrong. For example compare the output of + /usr/bin/time openssl speed ecdhp521 + on linux and hurd + most probably they are not implemented yet + they are all 0 + yes + should i report a bug to pkg time? + not sure + at least, there's this difference between eg amd64 and hurd-i386 + in configure's output: + -checking for wait3 that fills in rusage... yes + +checking for wait3 that fills in rusage... no + found this: + https://www.gnu.org/software/hurd/open_issues/time.html + seems related, yes + clopez: apparently all the ways to get the HZ define, either + directly or with CLOCKS_PER_SEC or CLK_TCK, so it gets defined as HZ + ... as 60, i mean (instead of 1000000) + $ ./time sleep 1 + 0.00user 0.00system 0:01.01elapsed 0PU (0avgtext+0avgdata + 0maxresident)k + :) + what it was? + i added the check for time.h, and included in the no-wait3 case + in resuse.c + (omg, the last release of gnu time was in 1997) + lol + hm not yet fixed + oh minor typo + clopez: http://paste.debian.net/246004/ + i will update the wiki page (on the hurd site) and send the + patch tomorrow + nice + yw, thanks again + i dropped the patch on debian/patches of pkg time.. rebuilt it + both on linux and hurd + and works as expected in both cases + i think you should forward the patch to the mantainer of pkg time + is there anyone maintaining gnu time? + http://packages.qa.debian.org/t/time.html + Maintainers for time are Bob Proulx . + that's the debian maintainer, yes, which is what i implied + earlier with "send the patch" + i guess that filling a bug against time with this patch attached + should be enough + yeah + wow... not only you fixed the elapsed time but also the other + variables :) + /usr/bin/time openssl speed ecdhp521 + now it reports cpu used and pagefaults :) + does it? + 10.00user 0.01system 0:10.11elapsed 99%CPU (0avgtext+0avgdata + 0maxresident)k + 0inputs+0outputs (67major+656minor)pagefaults 0swaps + + +# IRC, OFTC, #debian-hurd, 2013-03-31 + + clopez: #704283 -- cgit v1.2.3