Lines Matching full:layer
382 describing the link layer implemented by the interface (if any)
386 (Some trivial interfaces do not provide any link layer addresses;
531 A pointer to the common data for the interface's layer 2 protocol.
577 layer:
580 Pass a packet to an appropriate upper layer as determined
581 from the link-layer header of the packet.
586 can be shared among multiple drivers utilizing the same link-layer
652 for validity, and if necessary compute a link-layer group which
736 Control flags for the link layer.
972 Length of a link-layer address on this device, or zero if there are
979 Maximum length of any link-layer header which might be prepended by
986 sufficient space to prepend a link-layer header without allocating an
1000 link-layer overhead.
1049 Number of packets received which were sent by link-layer multicast.
1051 Number of packets sent by link-layer multicast.
1058 Number of packets received for unknown network-layer protocol.
1124 drivers should complete this structure by filling in their link-layer
1127 Other members of the structure represent network-layer addresses which
1191 to perform link-layer-specific actions upon requests to add,
1209 may also be link-layer support routines which are used by a number of
1210 drivers implementing a specific link layer over different hardware;
1211 see the documentation for that link layer for more details.
1215 link-layer multicast addresses (if any) should be accepted, and at a
1216 high level, in which network-layer multicast groups a user process has
1233 A pointer to the link-layer multicast address, if any, to which the
1234 network-layer multicast address in
1239 that link-layer address.
1277 addresses on that interface, and create a link-layer
1373 It is ordinarily only called from the socket-layer
1628 entry point to determine the link-layer address, if any, corresponding
1629 to this membership request, and also to give the link layer an
1639 routine returned a link-layer address corresponding to the group,