Lines Matching full:order
636 calls in order to unblock the thread, such as thread cancellation in
759 the latter three routines can be used directly in order to get the error
819 byte order, containing a PF_ value from
823 Note that ``host byte order'' is the byte order of the machine on which
826 done, ``host byte order'' is the byte order of the machine capturing the
828 the packets, but if a ``savefile'' is being read, the byte order and PF_
843 SLIP; the link layer header contains, in order:
910 byte order, containing a PF_ value from OpenBSD's
920 order:
923 a 2-byte "packet type", in network byte order, which is one of:
942 a 2-byte field, in network byte order, containing a Linux ARPHRD_ value
945 a 2-byte field, in network byte order, containing the length of the
952 order, or containing 1 for Novell 802.3 frames without an 802.2 LLC
960 OpenBSD pflog; the link layer header contains, in order:
963 a 1-byte header length, in host byte order;
965 a 4-byte PF_ value, in host byte order;
967 a 2-byte action code, in network byte order, which is one of:
980 a 2-byte reason code, in network byte order, which is one of:
1006 a 4-byte rule number, in network byte order;
1008 a 4-byte subrule number, in network byte order;
1010 a 1-byte direction, in network byte order, which is one of:
1032 SunATM devices; the link layer header contains, in order:
1038 low-order 4 bits, which is one of:
1065 a 2-byte VCI field, in network byte order.
1131 returns true if the current ``savefile'' uses a different byte order
