[40876] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: multi-homing fixes

daemon@ATHENA.MIT.EDU (Vijay Gill)
Fri Aug 24 03:32:19 2001

To: Roeland Meyer <rmeyer@mhsc.com>
Cc: 'Adam Rothschild' <asr@latency.net>, nanog@merit.edu
From: Vijay Gill <vgill@vijaygill.com>
Date: 24 Aug 2001 07:30:44 +0000
In-Reply-To: Roeland Meyer's message of "Thu, 23 Aug 2001 23:50:38 -0700"
Message-ID: <7mbsl5vrrv.fsf@challah.msrl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Errors-To: owner-nanog-outgoing@merit.edu


Roeland Meyer <rmeyer@mhsc.com> writes:

> |> From: Adam Rothschild [mailto:asr@latency.net]

> |> being accessed by lots of reading and writing processes.  RIB
> |> processing is substantial, and is only getting worse.
> 
> SMP systems and multi-ported RAM is a good enough stop-gap. If I didn't like
> non-deterministic systems, I might suggest Echelon technologies
> (hardware-based neural nets).


Roeland, what I believe Dr. Rothschild was alluding to is that the
underlying problem here is is more of fundamental database managment
problem. Key issues are concurrency controls involved in operating on
data that must be accessed by multiple readers and writers, among
other things.


> don't agree on, and am amazed to see, the admission that they don't
> know at what point the convergeince problem becomes intractible. Or
> even, if it does... that sounds more like a fundimental lack of
> understanding of the algorithm itself.

Large, distributed database systems are annoying and hard to deal
with, there is no silver bullet yet. This is something the DB folks
have been working on for years and since AS's can be viewed as a
distributed multiversion databases, no doubt there is much to be
learned from the research in the DB field.


/vijay


home help back first fref pref prev next nref lref last post