From: Andi Kleen <ak@suse•de>
To: Vojtech Pavlik <vojtech@suse•cz>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic•com>,
"Auke Kok" <sofar@foo-projects•org>,
"Auke Kok" <auke-jan.h.kok@intel•com>,
"Ingo Oeser" <ioe-lkml@rameria•de>,
"Jörn Engel" <joern@wohnheim•fh-wedel.de>,
"Ingo Oeser" <netdev@axxeo•de>,
"David S. Miller" <davem@davemloft•net>,
simlo@phys•au.dk, linux-kernel@vger•kernel.org, mingo@elte•hu,
netdev@vger•kernel.org
Subject: Re: Van Jacobson's net channels and real-time
Date: Tue, 2 May 2006 17:58:52 +0200 [thread overview]
Message-ID: <200605021758.52889.ak@suse.de> (raw)
In-Reply-To: <20060502124131.GA13160@suse.cz>
On Tuesday 02 May 2006 14:41, Vojtech Pavlik wrote:
> You seem to be missing the fact that most of todays interrupts are
> delivered through the APIC bus, which isn't fast at all.
You mean slow right? Modern x86s (anything newer than a P3) generally don't
have an separate APIC bus anymore but just send messages over their main
processor connection.
-Andi
next prev parent reply other threads:[~2006-05-02 16:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.0604201819040.19330-100000@lifa01.phys.au.dk>
2006-04-20 19:09 ` Van Jacobson's net channels and real-time David S. Miller
2006-04-21 16:52 ` Ingo Oeser
2006-04-22 11:48 ` Jörn Engel
2006-04-22 13:29 ` Ingo Oeser
2006-04-22 13:49 ` Jörn Engel
2006-04-23 0:05 ` Ingo Oeser
2006-04-23 5:50 ` David S. Miller
2006-04-24 16:42 ` Auke Kok
2006-04-24 16:59 ` linux-os (Dick Johnson)
2006-04-24 17:19 ` Rick Jones
2006-04-24 18:12 ` linux-os (Dick Johnson)
2006-04-24 23:17 ` Michael Chan
2006-04-25 1:49 ` Auke Kok
2006-04-25 11:29 ` linux-os (Dick Johnson)
2006-05-02 12:41 ` Vojtech Pavlik
2006-05-02 15:58 ` Andi Kleen [this message]
2006-04-23 5:52 ` David S. Miller
2006-04-23 9:23 ` Avi Kivity
2006-04-23 5:51 ` David S. Miller
2006-04-23 5:56 ` David S. Miller
2006-04-23 14:15 ` Ingo Oeser
2006-04-22 19:30 ` bert hubert
2006-04-23 5:53 ` David S. Miller
2006-04-24 17:28 Caitlin Bestler
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=200605021758.52889.ak@suse.de \
--to=ak@suse$(echo .)de \
--cc=auke-jan.h.kok@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=ioe-lkml@rameria$(echo .)de \
--cc=joern@wohnheim$(echo .)fh-wedel.de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-os@analogic$(echo .)com \
--cc=mingo@elte$(echo .)hu \
--cc=netdev@axxeo$(echo .)de \
--cc=netdev@vger$(echo .)kernel.org \
--cc=simlo@phys$(echo .)au.dk \
--cc=sofar@foo-projects$(echo .)org \
--cc=vojtech@suse$(echo .)cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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