Issue No. 01 - January (1994 vol. 20)
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/32.263751
<p>Analyses a multiround flow control algorithm that attempts to minimize the time required to multicast a message to a group of recipients and receive responses directly from each group member. Such a flow control algorithm may be necessary because the hurry of responses to the multicast can overflow the buffer space of the process that issued the multicast. The condition that each recipient directly respond to the multicast prevents the use of reliable multicast protocols based on software combining trees or negative-acknowledgments. The flow control analysed algorithm directs the responding processes to hold their responses for some period of time, called the backoff time, before sending them to the originator. The backoff time depends on the number of recipients that respond, the originator's available buffer space and buffer service time distribution, and the number of times that the originator is willing to retransmit its message. This paper develops an approximate analysis of the service time distribution of the limited-buffer preemptive queuing process that occurs within the protocol processing layers of a multiprogrammed operating system. It then uses this model to calculate multicast backoff times. The paper reports experimental verification of the accuracy of this service time model and discusses its application to the multicast flow control problem.</p>
telecommunications control; protocols; storage management; queueing theory; buffer storage; multiprogramming; network operating systems; multiround flow control algorithm; limited buffer multicast; buffer overflow; response holding; backoff time; recipients; available buffer space; buffer service time distribution; message retransmission; approximate analysis; service time distribution; limited-buffer preemptive queuing process; protocol processing layers; multiprogrammed operating system; accuracy
P. Danzig, "Flow Control for Limited Buffer Multicast," in IEEE Transactions on Software Engineering, vol. 20, no. , pp. 1-12, 1994.