summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOndrej Filip <feela@network.cz>2000-06-07 23:05:32 +0000
committerOndrej Filip <feela@network.cz>2000-06-07 23:05:32 +0000
commit37c3e558ab31a5e6088cef063dcd1e267238be74 (patch)
tree8381d966846ff15e46e254bc935bd775acb7f3fc
parent87f0d22ef84826f6dc6d0a1ae7ba8020b6e52573 (diff)
Simple explanation, how LSA are kept in database.
-rw-r--r--proto/ospf/ospf.c8
1 files changed, 6 insertions, 2 deletions
diff --git a/proto/ospf/ospf.c b/proto/ospf/ospf.c
index 9eec3092..a7fb650e 100644
--- a/proto/ospf/ospf.c
+++ b/proto/ospf/ospf.c
@@ -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.