Path: utzoo!attcan!uunet!mcvax!ukc!cam-cl!scc From: scc@cl.cam.ac.uk (Stephen Crawley) Newsgroups: comp.os.minix Subject: Re: Amoeba on Token Ring Message-ID: <762@scaup.cl.cam.ac.uk> Date: 30 May 89 00:43:16 GMT References: <16240@louie.udel.EDU> <760@scaup.cl.cam.ac.uk> Sender: news@cl.cam.ac.uk Distribution: comp Organization: U of Cambridge Comp Lab, UK Lines: 23 In <16240@louie.udel.EDU> cire@dustbin.cisco.com (Eric B. Decker) writes: > How do you figure that? Token Rings at least the IBM and IEEE 802.5 > versions sure do support broadcast. I stand corrected. I was generalising from my knowledge of rings (e.g. Cambridge Ring, CFR, etc) that do not support broadcast. So Amoeba on a token ring may be feasible. But don't blame me if your token ring bogs down with floods of broadcast packets :-). Seriously, in the "real" amoeba TP driver and the Amoeba/UNIX version, there is a pathological case where you see a lot of server locate broadcasts on the net. When the server does not have enough threads listening, a client request can arrive when the server is not ready. This causes the TP driver to drop/reject the packet, and the client's TP driver issues a locate. This will often happen when you have a single client thread trying to send a stream of data to a single server thread. One time, someone at Cambridge doing something like this with a handful of client/server pairs managed to bring our ethernet to its knees. My workstation was spending 100% of its time fending off Amoeba broadcasts. -- Steve