On Wednesday 12 December 2007 01:31:18 Rene Herman wrote:
> Good day.
>
> Would some people on x86 (both 32 and 64) be kind enough to compile and run
> the attached program? This is about testing how long I/O port access to port
> 0x80 takes. It measures in CPU cycles so CPU speed is crucial in reporting.
>
> Posted a previous incarnation of this before, buried in the outb 0x80 thread
> which had a serialising problem. This one should as far as I can see measure
> the right thing though. Please yell if you disagree...
>
> For me, on a Duron 1300 (AMD756 chipset) I have a constant:
>
> rene@7ixe4:~/src/port80$ su -c ./port80
> cycles: out 2400, in 2400
>
> and on a PII 400 (Intel 440BX chipset) a constant:
>
> rene@6bap:~/src/port80$ su -c ./port80
> cycles: out 553, in 251
>
> Results are (mostly) independent of compiler optimisation, but testing with
> an -O2 compile should be most useful. Thanks!
>
> Rene.
>
Sure,
maxim@MAIN:~/tmp$ sudo ./port800
cycles: out 1767, in 1147
maxim@MAIN:~/tmp$ sudo ./port800
cycles: out 1774, in 1148
maxim@MAIN:~/tmp$ sudo ./port800
cycles: out 1769, in 1150
maxim@MAIN:~/tmp$ sudo ./port800
cycles: out 1769, in 1150
maxim@MAIN:~/tmp$ sudo ./port800
cycles: out 1777, in 1150
maxim@MAIN:~/tmp$ sudo ./port800
cycles: out 1766, in 1149
maxim@MAIN:~/tmp$ sudo ./port800
cycles: out 1768, in 1148
maxim@MAIN:~/tmp$ sudo ./port800
cycles: out 1765, in 1147
Core 2 Duo system (ICH8/Intel DG965RY motherboard)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
