From: Rene Herman <rene.herman@gmail.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: 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: [RFT] Port 0x80 I/O speed
Date: Wed, 12 Dec 2007 00:31:18 +0100 [thread overview]
Message-ID: <475F1DC6.5090403@keyaccess.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
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.
[-- Attachment #2: port80.c --]
[-- Type: text/plain, Size: 1138 bytes --]
/* gcc -W -Wall -O2 -o port80 port80.c */
#include <stdlib.h>
#include <stdio.h>
#include <sys/io.h>
#define LOOPS 10000
inline unsigned long long rdtsc(void)
{
unsigned long long tsc;
asm volatile ("rdtsc": "=A" (tsc));
return tsc;
}
inline void serialize(void)
{
asm volatile ("cpuid": : : "eax", "ebx", "ecx", "edx");
}
int main(void)
{
unsigned long long start;
unsigned long long overhead;
unsigned long long output;
unsigned long long input;
int i;
if (iopl(3) < 0) {
perror("iopl");
return EXIT_FAILURE;
}
asm volatile ("cli");
start = rdtsc();
for (i = 0; i < LOOPS; i++) {
serialize();
serialize();
}
overhead = rdtsc() - start;
start = rdtsc() + overhead;
for (i = 0; i < LOOPS; i++) {
serialize();
asm volatile ("outb %al, $0x80");
serialize();
}
output = rdtsc() - start;
start = rdtsc() + overhead;
for (i = 0; i < LOOPS; i++) {
serialize();
asm volatile ("inb $0x80, %%al": : : "al");
serialize();
}
input = rdtsc() - start;
asm volatile ("sti");
output /= LOOPS;
input /= LOOPS;
printf("cycles: out %llu, in %llu\n", output, input);
return EXIT_SUCCESS;
}
next reply other threads:[~2007-12-11 23:33 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 23:31 Rene Herman [this message]
2007-12-11 23:40 ` [RFT] Port 0x80 I/O speed 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
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
-- strict thread matches above, loose matches on Subject: below --
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=475F1DC6.5090403@keyaccess.nl \
--to=rene.herman@gmail.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.