Lines Matching full:segments

536 	  segments from the same pool. Each segment is a 12 byte block,
539 	  Outgoing messages will allocate their segments at the start of the
542 	  segments at the start of the transaction, and won't release them until
546 	int "Maximum number of segments in incoming messages"
553 	  Maximum number of segments supported for incoming messages.
559 	  specification would allow (32 segments).
563 	  example, 5 segments means the maximum SDU size is 60 bytes,
568 	int "Maximum number of segments in outgoing messages"
575 	  Maximum number of segments supported for outgoing messages.
581 	  would allow (32 segments).
585 	  example, 5 segments means the maximum SDU size is 60 bytes,
590 	hex "Interval between sending two consecutive segments"
595 	  segments in a segmented message. The interval is measured in
615 	  acknowledgment with already confirmed segments was received.
618 	hex "Retransmissions interval step of missing segments to unicast address"
623 	  retransmissions of unacknowledged segments of a segmented message to
629 	hex "Retransmissions interval increment of missing segments to unicast address"
634 	  retransmissions of unacknowledged segments of a segmented message to
653 	  segments in a segmented message to a multicast address. The
663 	  This value defines a threshold in number of segments of a segmented
665 	  segments of a segmented message is above this threshold, the stack
676 	  receiving a new segment. The increment is measured in segments
681 	hex "Segments reception interval step"
685 	  This value defines the segments reception interval step used for
706 	  size of segments in a segmented message is above the
969 	  The actual maximum chunk size depends on how many segments are
997 	  The actual maximum chunk size depends on how many segments are