tiomap-dev team mailing list archive

[Rogelio Garcia <690821@xxxxxxxxxxxxxxxxxx>]

Hi Alexandros, 
I'm using the latest DDK 1.7 with a PandaBoard 2.0 and getting the following time when executing:

$ time eglinit

real	0m1.395s
user	0m0.047s
sys	0m0.242s

real	0m1.509s
user	0m0.016s
sys	0m0.273s

real	0m1.443s
user	0m0.008s
sys	0m0.281s

real	0m2.197s
user	0m0.070s
sys	0m0.164s

About the ioctl call I'm not seeing that many delays with the following command.
$ strace -c eglinit 
% time     seconds  usecs/call     calls    errors syscall
------ ----------- ----------- --------- --------- ----------------
 93.15    0.060150         269       224           mmap2
  3.92    0.002532           8       336         9 ioctl
  1.42    0.000916          19        49           munmap
  0.43    0.000275           1       247       170 open
  0.33    0.000214         214         1           socket
  0.33    0.000213           3        74           close
  0.24    0.000153           1       131        10 read
  0.19    0.000123          11        11        11 access
  0.00    0.000000           0        25           write
  0.00    0.000000           0         1           execve
  0.00    0.000000           0         3           brk
  0.00    0.000000           0         2           uname
  0.00    0.000000           0        42           mprotect
  0.00    0.000000           0        12           writev
  0.00    0.000000           0         1           nanosleep
  0.00    0.000000           0        23           poll
  0.00    0.000000           0         2           rt_sigaction
  0.00    0.000000           0         1           rt_sigprocmask
  0.00    0.000000           0         1           getrlimit
  0.00    0.000000           0        83        59 stat64
  0.00    0.000000           0        72           fstat64
  0.00    0.000000           0        10           geteuid32
  0.00    0.000000           0         7           fcntl64
  0.00    0.000000           0         7         1 futex
  0.00    0.000000           0         1           set_tid_address
  0.00    0.000000           0         1           connect
  0.00    0.000000           0         1           getpeername
  0.00    0.000000           0         1         1 set_robust_list
------ ----------- ----------- --------- --------- ----------------
100.00    0.064576                  1369       261 total
System call usage summary for 32 bit mode:
% time     seconds  usecs/call     calls    errors syscall
------ ----------- ----------- --------- --------- ----------------
   nan    0.000000           0         1           set_tls
------ ----------- ----------- --------- --------- ----------------
100.00    0.000000                     1           total

Do you think these times are acceptable??

-- 
You received this bug notification because you are a member of TI OMAP
Developers, which is subscribed to ubuntu-omap4-extras-graphics.
https://bugs.launchpad.net/bugs/690821

Title:
  Calling eglInitialize() takes too long

Status in Ubuntu OMAP4 graphics addons:
  New

Bug description:
  With the latest drivers on an SDP 4430 board calling eglInitialize
  takes extremely long. Running the example program (attached) on an
  completely idle system produces the following results:

  # time ./eglinit       
  real	0m5.797s
  user	0m0.008s
  sys	0m1.055s

  # time ./eglinit
  real	0m10.523s
  user	0m0.008s
  sys	0m1.047s

  # time ./eglinit
  real	0m30.459s
  user	0m0.008s
  sys	0m1.055s

  # time ./eglinit
  real	0m5.638s
  user	0m0.008s
  sys	0m1.055s

  # time ./eglinit
  real	0m10.088s
  user	0m0.008s
  sys	0m1.047s

  I have attached an strace capture of a sample run that shows that the
  delay is happening in an ioctl() around line 10000.

  The trace also shows that the driver wastes a lot of time trying out
  /dev/dri/* devices, but that is another subject :)