From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "David S. Miller" <davem@redhat.com>,
hadi@cyberus.ca, akpm@digeo.com, manfred@colorfullife.com,
netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Info: NAPI performance at "low" loads
Date: 19 Sep 2002 16:53:02 +0100 [thread overview]
Message-ID: <1032450782.27721.5.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <m18z1ykoms.fsf@frodo.biederman.org>
On Thu, 2002-09-19 at 16:03, Eric W. Biederman wrote:
> If I do an inb to a PCI-X device running at 133Mhz it should come back
> much faster than an inb from my serial port on the ISA port. What
> is the reason for the fixed minimum timing?
As far as I can tell the minimum time for the inb/outb is simply the
time it takes the bus to respond. The only difference there is that for
writel rather than outl you won't wait for the write to complete on the
PCI bus just dump it into the fifo if its empty
prev parent reply other threads:[~2002-09-19 15:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 19:53 Info: NAPI performance at "low" loads Manfred Spraul
2002-09-17 20:59 ` David S. Miller
2002-09-17 21:32 ` Andrew Morton
2002-09-17 21:26 ` David S. Miller
2002-09-17 21:45 ` Andrew Morton
2002-09-17 21:39 ` David S. Miller
2002-09-17 21:54 ` Jeff Garzik
2002-09-17 21:49 ` David S. Miller
2002-09-18 2:11 ` Jeff Garzik
2002-09-18 2:06 ` David S. Miller
2002-09-18 2:36 ` Jeff Garzik
2002-09-17 21:58 ` Andrew Morton
2002-09-18 0:57 ` jamal
2002-09-18 1:00 ` David S. Miller
2002-09-18 2:16 ` Andrew Morton
2002-09-18 17:27 ` Eric W. Biederman
2002-09-18 17:50 ` Alan Cox
2002-09-19 14:58 ` Eric W. Biederman
2002-09-18 20:23 ` David S. Miller
2002-09-18 20:43 ` Alan Cox
2002-09-18 20:46 ` David S. Miller
2002-09-18 21:15 ` Alan Cox
2002-09-18 21:22 ` David S. Miller
2002-09-19 15:03 ` Eric W. Biederman
2002-09-19 15:53 ` Alan Cox [this message]
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=1032450782.27721.5.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@digeo.com \
--cc=davem@redhat.com \
--cc=ebiederm@xmission.com \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=netdev@oss.sgi.com \
/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).