From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Van Jacobson's net channels and real-time
Date: Mon, 24 Apr 2006 17:48:41 -0600 [thread overview]
Message-ID: <444D63D9.8060804@shaw.ca> (raw)
In-Reply-To: <65cJF-66i-11@gated-at.bofh.it>
linux-os (Dick Johnson) wrote:
> Message signaled interrupts are just a kudge to save a trace on a
> PC board (read make junk cheaper still). They are not faster and
> may even be slower.
Save a trace on the PC board? How about no, since the devices still need
to support INTX interrupts anyway. And yes, they can be faster, mainly
because being an in-band signal it simplifies some PCI posting related
issues, and there is no need to worry about sharing.
> They will not be the salvation of any interrupt
> latency problems. The solutions for increasing networking speed,
> where the bit-rate on the wire gets close to the bit-rate on the
> bus, is to put more and more of the networking code inside the
> network board. The CPU get interrupted after most things (like
> network handshakes) are complete.
You mean like these?
http://linux-net.osdl.org/index.php/TOE
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-04-24 23:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <63KcN-6lD-25@gated-at.bofh.it>
[not found] ` <64wrg-2cg-41@gated-at.bofh.it>
[not found] ` <64wAE-2Cs-9@gated-at.bofh.it>
[not found] ` <64AkV-8cG-7@gated-at.bofh.it>
[not found] ` <65cqo-5tR-33@gated-at.bofh.it>
[not found] ` <65cJF-66i-11@gated-at.bofh.it>
2006-04-24 23:48 ` Robert Hancock [this message]
2006-04-24 17:28 Van Jacobson's net channels and real-time Caitlin Bestler
-- strict thread matches above, loose matches on Subject: below --
2006-04-20 16:29 Esben Nielsen
2006-04-20 19:09 ` 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
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-21 8:53 ` Jan Kiszka
2006-04-24 14:22 ` Esben Nielsen
2006-04-27 8:09 ` Jan Kiszka
2006-04-27 8:16 ` David S. Miller
2006-04-27 10:00 ` Jan Kiszka
2006-04-27 19:50 ` David S. Miller
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=444D63D9.8060804@shaw.ca \
--to=hancockr@shaw.ca \
--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 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.