From: Pavel Machek <pavel@ucw.cz>
To: "Filipau, Ihar" <ifilipau@sussdd.de>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: inw/outw performance
Date: Sun, 30 Mar 2003 19:23:06 +0200 [thread overview]
Message-ID: <20030330172306.GA6666@zaurus.ucw.cz> (raw)
In-Reply-To: <7A5D4FEED80CD61192F2001083FC1CF9065148@CHARLY>
Hi!
> And actually what I have found that on my development P3/1GHz system
> every inw() takes more that 3us. I wasn't measuring outw() yet - but
> I do not expect its timing to be better.
inw/outw *is* slow. Memory map your
registers to speed it up.
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
next prev parent reply other threads:[~2003-03-30 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 8:00 Filipau, Ihar
2003-03-30 17:23 ` Pavel Machek [this message]
2003-03-30 20:32 ` Jonathan Lundell
2003-03-31 8:41 Filipau, Ihar
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=20030330172306.GA6666@zaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=ifilipau@sussdd.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®