04ac848d6f
between protocol handlers. ipsec socket pointers, ipsec decryption/auth information, tunnel decapsulation information are in my mind - there can be several other usage. at this moment, we use this for ipsec socket pointer passing. this will avoid reuse of m->m_pkthdr.rcvif in ipsec code. due to the change, MHLEN will be decreased by sizeof(void *) - for example, for i386, MHLEN was 100 bytes, but is now 96 bytes. we may want to increase MSIZE from 128 to 256 for some of our architectures. take caution if you use it for keeping some data item for long period of time - use extra caution on M_PREPEND() or m_adj(), as they may result in loss of m->m_pkthdr.aux pointer (and mbuf leak). this will bump kernel version. (as discussed in tech-net, tested in kame tree) |
||
|---|---|---|
| .. | ||
| xebec | ||
| argo_debug.h | ||
| clnl.h | ||
| clnp_debug.c | ||
| clnp_er.c | ||
| clnp_frag.c | ||
| clnp_input.c | ||
| clnp_options.c | ||
| clnp_output.c | ||
| clnp_raw.c | ||
| clnp_stat.h | ||
| clnp_subr.c | ||
| clnp_timer.c | ||
| clnp.h | ||
| cltp_usrreq.c | ||
| cltp_var.h | ||
| cons_pcb.h | ||
| cons.h | ||
| eonvar.h | ||
| esis.c | ||
| esis.h | ||
| idrp_usrreq.c | ||
| idrp_var.h | ||
| if_cons.c | ||
| if_eon.c | ||
| iso_chksum.c | ||
| iso_errno.h | ||
| iso_pcb.c | ||
| iso_pcb.h | ||
| iso_proto.c | ||
| iso_snpac.c | ||
| iso_snpac.h | ||
| iso_var.h | ||
| iso.c | ||
| iso.h | ||
| Makefile | ||
| README | ||
| tp_astring.c | ||
| tp_clnp.h | ||
| tp_cons.c | ||
| tp_driver.c | ||
| tp_emit.c | ||
| tp_events.h | ||
| tp_inet.c | ||
| tp_input.c | ||
| tp_ip.h | ||
| tp_iso.c | ||
| tp_meas.c | ||
| tp_meas.h | ||
| tp_output.c | ||
| tp_param.h | ||
| tp_pcb.c | ||
| tp_pcb.h | ||
| tp_seq.h | ||
| tp_stat.h | ||
| tp_states.h | ||
| tp_states.init | ||
| tp_subr2.c | ||
| tp_subr.c | ||
| tp_timer.c | ||
| tp_timer.h | ||
| tp_tpdu.h | ||
| tp_trace.c | ||
| tp_trace.h | ||
| tp_user.h | ||
| tp_usrreq.c | ||
| tp_var.h | ||
| tp.trans | ||
In case you were wondering why this code is still present: The ISO (or OSI) stack is still in use by many router vendors (e.g., using IS-IS the OSI equivelent of OSPF, to carry IP routes). Chris. chopps@netbsd.org