CVSROOT: /cvs
Module name: src
Changes by: [email protected] 2016/05/17 21:46:03
Modified files:
share/man/man9 : srp_enter.9 srpl_rc_init.9
sys/kern : kern_srp.c
sys/net : bpf.c if.c if_vlan.c rtable.c
sys/netinet : ip_carp.c
sys/sys : srp.h
Log message:
rework the srp api so it takes an srp_ref struct that the caller provides.
the srp_ref struct is used to track the location of the callers
hazard pointer so later calls to srp_follow and srp_enter already
know what to clear. this in turn means most of the caveats around
using srps go away. specifically, you can now:
- switch cpus while holding an srp ref
- ie, you can sleep while holding an srp ref
- you can take and release srp refs in any order
the original intent was to simplify use of the api when dealing
with complicated data structures. the caller now no longer has to
track the location of the srp a value was fetched from, the srp_ref
effectively does that for you.
srp lists have been refactored to use srp_refs instead of srpl_iter
structs.
this is in preparation of using srps inside the ART code. ART is a
complicated data structure, and lookups require overlapping holds
of srp references.
ok mpi@ jmatthew@
