Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 15 Jul 2002 12:30:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 15 Jul 2002 12:30:44 -0400 Received: from zcars04e.nortelnetworks.com ([47.129.242.56]:13477 "EHLO zcars04e.ca.nortel.com") by vger.kernel.org with ESMTP id ; Mon, 15 Jul 2002 12:30:42 -0400 Message-ID: <3D32F959.A43EFA72@nortelnetworks.com> Date: Mon, 15 Jul 2002 12:33:29 -0400 X-Sybari-Space: 00000000 00000000 00000000 From: Chris Friesen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.18 i686) X-Accept-Language: en MIME-Version: 1.0 To: Sandy Harris Cc: linux-kernel@vger.kernel.org Subject: Re: [patch[ Simple Topology API References:

<20020714214334.A16892@wotan.suse.de> <3D32E97A.AD808E43@storm.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1003 Lines: 28 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/