netdev
[Top] [All Lists]

Re: Protocol specific data in the FIB

To: jamal <hadi@xxxxxxxxxx>
Subject: Re: Protocol specific data in the FIB
From: "James R. Leu" <jleu@xxxxxxxxxxxxxx>
Date: Sun, 27 Aug 2000 13:27:00 -0500
Cc: netdev@xxxxxxxxxxx
In-reply-to: <Pine.GSO.4.20.0008262252390.10165-100000@shell.cyberus.ca>; from jamal on Sat, Aug 26, 2000 at 10:56:57PM -0400
Organization: none
References: <20000826201342.C32166@doit.wisc.edu> <Pine.GSO.4.20.0008262252390.10165-100000@shell.cyberus.ca>
Reply-to: jleu@xxxxxxxxxxxxxx
Sender: owner-netdev@xxxxxxxxxxx
The URL for MPLS for Linux is:

http://nero.doit.wisc.edu/mpls-linux/

Follow the link to the FTP site and grab linux-mpls-ldp-0.202.tar.gz.

If you look at linux-mpls-ldp/kernel/mpls.diff you'll see the modifications
to fib_hash.c and fib_rules.c.

Jim

On Sat, Aug 26, 2000 at 10:56:57PM -0400, jamal wrote:
> 
> 
> On Sat, 26 Aug 2000, James R. Leu wrote:
> 
> > For protocols that live somewhere between layer 2 and layer 3 they have some
> > unique needs from the layer 3 protocols.
> > 
> > To be specific MPLS needs to store labelling information for each entry in 
> > the
> > FIB.  If the FIB had a protocol specific field (or set of fields) and a set
> > of access functions for these fields then MPLS wouldn't have to be so 
> > intrusive
> > in the FIB code.
> > 
> > I have code that already meets the needs of MPLS but would like to get
> > feedback from the list:
> > 
> > -Are there other protocols that could take advantage of protocol specific
> >  fields in the FIB?
> > -Is this even a good idea?
> > 
> 
> If i remember correctly you (could you post the URL?) only mod-ed fib_nh
> and fib_result to contain the mpls specific data?
> fib_nh makes sense because a label is a nh specific detail and fib_result
> because you need the result for further processing. 
> post the URL
> 
> cheers,
> jamal

-- 
James R. Leu

<Prev in Thread] Current Thread [Next in Thread>