Lines Matching full:bandwidth
678 .\" 4. Mechanism for "multicast bandwidth monitoring and upcalls".
682 forwarding bandwidth for some data flow.
685 the bandwidth rate is above a threshold for example.
687 The original solution for measuring the bandwidth of a dataflow was
691 has been idle, or whether the source's transmission bandwidth is above a
694 mechanism for bandwidth monitoring.
696 Below is a description of the bandwidth monitoring mechanism.
699 If the bandwidth of a data flow satisfies some pre-defined filter,
703 The bandwidth-upcall filters are installed per (S,G).
720 The bandwidth-upcall mechanism is enabled by
726 The bandwidth-upcall filters are added/deleted by the new
740 * measured bandwidth is above or below a threshold.
743 * bandwidth used by some data flow is above or below some threshold.
791 /* min. threshold time interval for bandwidth measurement */
816 SEND_UPCALL("measured bandwidth is >= threshold");
823 SEND_UPCALL("measured bandwidth is <= threshold");
832 Basically, an upcall is delivered if the measured bandwidth is >= or
833 <= the threshold bandwidth (within the specified measurement
837 If smaller values are allowed, then the bandwidth
882 To delete all bandwidth filters for a given (S,G), then
894 The bandwidth upcalls are received by aggregating them in the new upcall
927 the exact value of the bandwidth of the forwarded data.
928 To measure the exact bandwidth, the user would need to
997 The advanced multicast API and the multicast bandwidth