From: "David S. Miller" <davem@redhat.com>
To: ebiederm@xmission.com
Cc: 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: Wed, 18 Sep 2002 13:23:34 -0700 (PDT) [thread overview]
Message-ID: <20020918.132334.102949210.davem@redhat.com> (raw)
In-Reply-To: <m1hegnky2h.fsf@frodo.biederman.org>
From: ebiederm@xmission.com (Eric W. Biederman)
Date: 18 Sep 2002 11:27:34 -0600
"David S. Miller" <davem@redhat.com> writes:
> {in,out}{b,w,l}() operations have a fixed timing, therefore his
> results doesn't sound that far off.
????
I don't see why they should be. If it is a pci device the cost should
the same as a pci memory I/O. The bus packets are the same. So things like
increasing the pci bus speed should make it take less time.
The x86 processor has a well defined timing for executing inb
etc. instructions, the timing is fixed and is independant of the
speed of the PCI bus the device is on.
next prev parent reply other threads:[~2002-09-18 20:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D879F59.6BDF9443@digeo.com>
[not found] ` <20020917.142635.114214508.davem@redhat.com>
2002-09-17 21:45 ` Info: NAPI performance at "low" loads 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 [this message]
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
2002-09-17 19:54 Manfred Spraul
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=20020918.132334.102949210.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@digeo.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).