Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!ucsd!ucsdhub!hp-sdd!ncr-sd!ncrcae!hubcap!wen-king From: wen-king@csvax.caltech.edu (Wen-King Su) Newsgroups: comp.parallel Subject: Re: scalability of n-cubes, meshes Message-ID: <7275@hubcap.clemson.edu> Date: 1 Dec 89 13:55:00 GMT Sender: fpst@hubcap.clemson.edu Lines: 24 Approved: parallel@hubcap.clemson.edu >From Donald.Lindsay@MATHOM.GANDALF.CS.CMU.EDU routing latency per hop. I don't agree: wider is faster. The reason until it has seen the entirety of the packet header. On an NCUBE-2, (44, to be precise). A byte-wide path, such as BBN uses, could make header's likeliest command mode was decodable from, say, the first