Lines Matching full:layer

195 describing the link layer implemented by the interface (if any)
199 (Some trivial interfaces do not provide any link layer addresses;
226 A pointer to the common data for the interface's layer 2 protocol.
467 layer:
470 Pass a packet to an appropriate upper layer as determined
471 from the link-layer header of the packet.
476 can be shared among multiple drivers utilizing the same link-layer
542 for validity, and if necessary compute a link-layer group which
626 Control flags for the link layer.
862 Length of a link-layer address on this device, or zero if there are
869 Maximum length of any link-layer header which might be prepended by
876 sufficient space to prepend a link-layer header without allocating an
890 link-layer overhead.
951 Number of packets received which were sent by link-layer multicast.
953 Number of packets sent by link-layer multicast.
960 Number of packets received for unknown network-layer protocol.
1027 drivers should complete this structure by filling in their link-layer
1030 Other members of the structure represent network-layer addresses which
1094 to perform link-layer-specific actions upon requests to add,
1112 may also be link-layer support routines which are used by a number of
1113 drivers implementing a specific link layer over different hardware;
1114 see the documentation for that link layer for more details.
1118 link-layer multicast addresses (if any) should be accepted, and at a
1119 high level, in which network-layer multicast groups a user process has
1136 A pointer to the link-layer multicast address, if any, to which the
1137 network-layer multicast address in
1142 that link-layer address.
1180 addresses on that interface, and create a link-layer
1276 It is ordinarily only called from the socket-layer
1531 entry point to determine the link-layer address, if any, corresponding
1532 to this membership request, and also to give the link layer an
1542 routine returned a link-layer address corresponding to the group,