From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Sandy Harris <pashley@storm.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch[ Simple Topology API
Date: Mon, 15 Jul 2002 12:33:29 -0400 [thread overview]
Message-ID: <3D32F959.A43EFA72@nortelnetworks.com> (raw)
In-Reply-To: <3D32E97A.AD808E43@storm.ca>
Sandy Harris wrote:
> I suspect latency may become an issue when more than one link is
> involved and there can be contention.
According to the AMD talk at OLS, worst case on a 4-way is better than current
best-case on a uniprocessor athlon.
> Beyond 8-way, you need glue logic (hypertransport switches?) and
> latency seems bound to become an issue.
Nope. Just extend the ladder. Each cpu talks to three other entities, either
cpu or I/O. Can be extended arbitrarily until latencies are too high.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2002-07-15 16:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D2F75D7.3060105@us.ibm.com.suse.lists.linux.kernel>
[not found] ` <3D2F9521.96D7080B@zip.com.au.suse.lists.linux.kernel>
2002-07-13 20:08 ` Andi Kleen
2002-07-14 19:17 ` Linus Torvalds
2002-07-14 19:43 ` Andi Kleen
2002-07-15 2:34 ` Eric W. Biederman
2002-07-15 15:25 ` Sandy Harris
2002-07-15 16:33 ` Chris Friesen [this message]
2002-07-16 10:30 ` Eric W. Biederman
2002-07-16 12:59 ` Rik van Riel
2002-07-16 15:45 ` Martin J. Bligh
2002-07-16 19:03 ` Martin J. Bligh
2002-07-16 22:29 ` Matthew Dobson
2002-07-17 0:21 ` Michael Hohnbaum
2002-07-15 17:48 ` Matthew Dobson
2002-07-15 19:50 Jukka Honkela
-- strict thread matches above, loose matches on Subject: below --
2002-07-13 0:35 Matthew Dobson
2002-07-13 2:49 ` Andrew Morton
2002-07-15 18:49 ` Matthew Dobson
2002-07-13 8:04 ` Alexander Viro
2002-07-13 17:13 ` Albert D. Cahalan
2002-07-15 23:52 ` Matthew Dobson
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=3D32F959.A43EFA72@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pashley@storm.ca \
/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®