Jerry/bird
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Simple explanation, how LSA are kept in database.

Browse source
This commit is contained in:
Ondrej Filip 2000-06-07 23:05:32 +00:00
parent 87f0d22ef8
commit 37c3e558ab
1 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
proto/ospf/ospf.c
View file

@ -29,7 +29,8 @@
* adding and deleting them, there are also functions for originating
* various types of LSA. (router lsa, net lsa, external lsa) |Rt.c|
* contains routins for calculating of routing table. |Lsalib.c| is a set
* of various functions for work with LSAs.
* of various functions for work with LSAs. (Endianity transformations,
* checksum calculation etc.)
*
* Just one instance of protocol is able to hold LSA databases for
* multiple OSPF areas and exhange routing information between
@ -38,7 +39,10 @@
* &ospf_iface are connected. To &ospf_area is connected
* &top_hash_graph, which is a dynamic hashing structure that
* describes link-state database. It allows fast search, adding
* and deleting. Every area has it's own area_disp() that is
* and deleting. LSA is kept in two pieces: header and body. Both of them are
* kept in endianity of CPU.
*
* Every area has it's own area_disp() that is
* responsible for late originating of router LSA, calcutating
* of routing table and it also ages and flushes LSA database. This
* function is called in regular intervals.