Home
last modified time | relevance | path

Searched hist:dcb17c31 (Results 1 – 20 of 20) sorted by relevance

/openbsd/sys/net/
H A Dif_pppoe.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Dif_loop.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Dif_ppp.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Dif_gif.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Dif_pppx.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Dif_gre.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Dif_var.hdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Dif_spppsubr.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Dif_tun.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Dif_ethersubr.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Drtsock.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Droute.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Dif.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
/openbsd/sys/netinet/
H A Dif_ether.hdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Dif_ether.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Dip_carp.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
/openbsd/sys/netinet6/
H A Dnd6.hdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Dnd6_rtr.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Dnd6.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@
H A Din6.cdcb17c31 Sun Oct 25 11:58:11 GMT 2015 mpi <mpi@openbsd.org> Introduce if_rtrequest() the successor of ifa_rtrequest().

L2 resolution depends on the protocol (encoded in the route entry) and
an ``ifp''. Not having to care about an ``ifa'' makes our life easier
in our MP effort. Fewer dependencies between data structures implies
fewer headaches.

Discussed with bluhm@, ok claudio@