Lines Matching refs:segments

538 	  segments from the same pool. Each segment is a 12 byte block,
541 	  Outgoing messages will allocate their segments at the start of the
544 	  segments at the start of the transaction, and won't release them until
548 	int "Maximum number of segments in incoming messages"
555 	  Maximum number of segments supported for incoming messages.
561 	  specification would allow (32 segments).
565 	  example, 5 segments means the maximum SDU size is 60 bytes,
570 	int "Maximum number of segments in outgoing messages"
577 	  Maximum number of segments supported for outgoing messages.
583 	  would allow (32 segments).
587 	  example, 5 segments means the maximum SDU size is 60 bytes,
592 	hex "Interval between sending two consecutive segments"
597 	  segments in a segmented message. The interval is measured in
617 	  acknowledgment with already confirmed segments was received.
620 	hex "Retransmissions interval step of missing segments to unicast address"
625 	  retransmissions of unacknowledged segments of a segmented message to
631 	hex "Retransmissions interval increment of missing segments to unicast address"
636 	  retransmissions of unacknowledged segments of a segmented message to
655 	  segments in a segmented message to a multicast address. The
665 	  This value defines a threshold in number of segments of a segmented
667 	  segments of a segmented message is above this threshold, the stack
678 	  receiving a new segment. The increment is measured in segments
687 	  This value defines the segments reception interval step used for
708 	  size of segments in a segmented message is above the
971 	  The actual maximum chunk size depends on how many segments are
999 	  The actual maximum chunk size depends on how many segments are