Re: KSTAR and atalkad, atis.

Article View: comp.protocols.appletalk

Article #5272

Back to comp.protocols.appletalk Previous Next

#5272

From: morgan
Date: Tue, 20 Dec 1988 17:49

18 lines
1153 bytes

Greg Minshall writes:

> K-STAR has no hard limits on the number of zones, zone names, etc.

One advantage of the "hard limits" in KIP is that we know when things
will break (we took action when we realized we had 63 nets in our
atalkatab, for example).  While I have faith that the 256K memory in
the KFPS-4 will allow any of the K* tables to grow as much as we may
want, I'm not so sanguine about the 80(?)K memory in the KFPS-[123]
with the recently announced memory upgrade.  Is there any way we can
tell if K* tables overflow?  Is there a formula for totting up all the
entries in all the relevant tables and comparing against a total
heap-space size, or something?

 - RL "Bob" Morgan
   Networking Systems
   Stanford

Technical Details

Message-ID: <Added.UXfd=Ky00UkTE8EU9k@andrew.cmu.edu>

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!ncrlnk!ncrcae!hubcap!gatech!rutgers!ucsd!ucbvax!JESSICA.STANFORD.EDU!morgan

References: <682@kinetics.UUCP>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!ncrlnk!ncrcae!hubcap!gatech!rutgers!ucsd!ucbvax!JESSICA.STANFORD.EDU!morgan
From: morgan@JESSICA.STANFORD.EDU
Newsgroups: comp.protocols.appletalk
Subject: Re: KSTAR and atalkad, atis.
Message-ID: <Added.UXfd=Ky00UkTE8EU9k@andrew.cmu.edu>
Date: 20 Dec 88 17:49:34 GMT
References: <682@kinetics.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 18

Reply to Parent Message