linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Rene Herman <rene.herman@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	dpreed@reed.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	pavel@ucw.cz, andi@firstfloor.org, rol@as2917.net,
	Krzysztof Halasa <khc@pm.waw.pl>,
	david@davidnewall.com, hpa@zytor.com, john@stoffel.org,
	linux-os@analogic.com
Subject: Re: [RFT] Port 0x80 I/O speed
Date: Wed, 12 Dec 2007 11:28:07 +0100	[thread overview]
Message-ID: <1197455287.6985.35.camel@twins> (raw)
In-Reply-To: <475F1DC6.5090403@keyaccess.nl>


On Wed, 2007-12-12 at 00:31 +0100, 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!

Since a lot of people reported timings for all the fancy new x86_64
hardware, I've not included those. Timings for my ancient machines still
in service:

$ gcc -o port80 -O2 port80.c
$ sudo ./port80
cycles: out 1736, in 1735
$ sudo ./port80
cycles: out 1831, in 1827
$ sudo ./port80
cycles: out 1735, in 1735
$ sudo ./port80
cycles: out 1743, in 1737
$ sudo ./port80
cycles: out 1737, in 1734

$ cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 6
model name      : AMD Athlon(tm) MP 1800+
stepping        : 2
cpu MHz         : 1533.420
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov
pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow ts
bogomips        : 3069.09
clflush size    : 32

processor       : 1
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 6
model name      : AMD Athlon(tm) Processor
stepping        : 2
cpu MHz         : 1533.420
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov   pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow ts
bogomips        : 3067.07
clflush size    : 32


---

# ./port80
cycles: out 812, in 354
# ./port80
cycles: out 811, in 354
# ./port80
cycles: out 811, in 354
# ./port80
cycles: out 811, in 354

# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 8
model name      : Pentium III (Coppermine)
stepping        : 1
cpu MHz         : 672.071
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 mmx fxsr sse
bogomips        : 1331.20


---


# ./port80
cycles: out 116, in 47
# ./port80
cycles: out 116, in 47
# ./port80
cycles: out 116, in 47
# ./port80
cycles: out 116, in 47

# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 5
model           : 2
model name      : Pentium 75 - 200
stepping        : 12
cpu MHz         : 99.476
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : yes
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr mce cx8
bogomips        : 198.24


P133 clocked at 100MHz


  parent reply	other threads:[~2007-12-12 10:28 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 23:31 [RFT] Port 0x80 I/O speed Rene Herman
2007-12-11 23:40 ` Maxim Levitsky
2007-12-11 23:44   ` Rene Herman
2007-12-12  0:14     ` Maxim Levitsky
2007-12-12  0:27       ` Rene Herman
2007-12-11 23:43 ` Alejandro Riveira Fernández
2007-12-11 23:51   ` Rene Herman
2007-12-12  0:09     ` Alejandro Riveira Fernández
2007-12-12  0:16       ` Rene Herman
2007-12-12 11:43         ` Alejandro Riveira Fernández
2007-12-12 21:02         ` H. Peter Anvin
     [not found]   ` <Pine.LNX.4.61.0712120753210.4443@chaos.analogic.com>
2007-12-12 13:20     ` Rene Herman
2007-12-12 13:23       ` linux-os (Dick Johnson)
2007-12-11 23:55 ` Nigel Cunningham
2007-12-12  0:01   ` Rene Herman
2007-12-12  2:07     ` Nigel Cunningham
2007-12-12  1:19 ` Alistair John Strachan
2007-12-12  1:28 ` Randy Dunlap
2007-12-12  1:40 ` Mike Lampard
2007-12-12  5:23 ` Kyle McMartin
2007-12-12  7:18   ` Rene Herman
2007-12-13  2:41     ` H. Peter Anvin
2007-12-12 19:25   ` H. Peter Anvin
2007-12-12 19:32     ` Andi Kleen
2007-12-12 19:43       ` H. Peter Anvin
2007-12-12  8:17 ` Paolo Ornati
2007-12-12  8:38   ` Edwin de Caluwé
2007-12-12  8:35 ` Dave Young
2007-12-12  8:48 ` Jiri Slaby
2007-12-12 11:25   ` Jiri Slaby
2007-12-12 15:50     ` Rene Herman
2007-12-12 15:53     ` Rene Herman
2007-12-12 18:44     ` H. Peter Anvin
2007-12-12 19:19       ` Rene Herman
2007-12-13 15:19         ` Jiri Slaby
2007-12-12  8:59 ` Juergen Beisert
2007-12-12 14:30   ` Rene Herman
2007-12-12 15:12     ` Juergen Beisert
2007-12-12  9:55 ` Luciano Rocha
2007-12-12  9:57 ` Romano Giannetti
2007-12-12 16:27   ` Rene Herman
2007-12-12 10:28 ` Peter Zijlstra [this message]
2007-12-12 10:34 ` Dave Haywood
2007-12-12 11:57 ` Ville Syrjälä
2007-12-13 16:42   ` Ville Syrjälä
2007-12-12 16:16 ` John Stoffel
2007-12-12 16:39 ` Olivér Pintér
2007-12-12 16:53 ` Ondrej Zary
2007-12-12 17:00   ` H. Peter Anvin
2007-12-12 16:59 ` Cyrill Gorcunov
2007-12-12 17:27 ` Török Edwin
2007-12-12 18:54   ` David P. Reed
2007-12-12 18:39 ` SL Baur
2007-12-12 19:06   ` Rene Herman
2007-12-12 21:32 ` Jesper Juhl
2007-12-12 23:54 ` Jan Engelhardt
2007-12-13  0:13   ` Jan Engelhardt
2007-12-13  2:06   ` H. Peter Anvin
2007-12-22 22:27 ` Bauke Jan Douma
2007-12-12  5:06 Chris Holvenstot
2007-12-12 11:20 linux
2007-12-12 12:35 ` Paolo Ornati
2007-12-12 14:48 ` Rene Herman
     [not found] <9zmRR-3pA-25@gated-at.bofh.it>
2007-12-13 16:27 ` James Kosin
2007-12-13 22:07   ` Rene Herman
2007-12-13 22:30     ` Jesper Juhl
2007-12-13 22:37       ` Rene Herman
     [not found] <9A0cz-7xy-13@gated-at.bofh.it>
     [not found] ` <9A0cz-7xy-11@gated-at.bofh.it>
     [not found]   ` <9A4pU-69z-15@gated-at.bofh.it>
2007-12-14 14:08     ` James Kosin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1197455287.6985.35.camel@twins \
    --to=peterz@infradead.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andi@firstfloor.org \
    --cc=david@davidnewall.com \
    --cc=dpreed@reed.com \
    --cc=hpa@zytor.com \
    --cc=john@stoffel.org \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=pavel@ucw.cz \
    --cc=rene.herman@gmail.com \
    --cc=rol@as2917.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).