Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

How the RSVP Service Invokes TC

[RSVP signaling is not supported except on Windows 2000. See RSVP Operates Only on Windows 2000 for more information.]

The RSVP service and TC communicate in order to work together to provide overall quality of service for a given sending flow. When an application requests quality of service using the RSVP SP, the RSVP SP responds by initiating RSVP signaling and invoking kernel traffic control from local TC components (using the traffic control Interface). As such, traffic control and RSVP signaling are initiated concurrently upon flow setup.

In this transitional period (presuming QOS_SD_MODE has not been specifically set) the reservation has not been established, and therefore traffic control is configured to transmit traffic associated with the flow's specification, as follows:

  • BEST_EFFORT traffic is transmitted with its QOS_SD_MODE set to borrow mode (TC_NONCONF_BORROW)
  • CONTROLLED LOAD traffic is transmitted with its QOS_SD_MODE set to TC_NONCONF_BORROW
  • GUARANTEED traffic is shaped with its QOS_SD_MODE set to TC_NONCONF_SHAPE
Note  The above default configuration can be overridden by supplying the QOS_SD_MODE object in the ProviderSpecific buffer.

In this transitional period, all packets conforming to the flowspec for BEST_EFFORT and CONTROLLED LOAD are sent immediately with the appropriate traffic control marking, and nonconforming packets are sent immediately with their host and network priority demoted. Transmission settings for any given flow are aligned with the allowed sending rate specified by the system (which is in turn determined by settings in the appropriate FLOWSPEC).

Sending applications can determine what the allowed sending rate is by querying the Allowed_Rate using SIO_CHK_QOS. More information about using SIO_CHK_QOS is provided in Using SIO_CHK_QOS.

Once PATH messages arrive at the receiving host (or hosts; for simplicity, ongoing references will be singular), the host may request QOS provisioning for the flow in the form of RESV messages sent back toward the sender. When the RSVP SP on the receiver receives the RESV message, it communicates with traffic control to enable traffic control to update its transmission information, and if appropriate, to modify the BEST_EFFORT flow according to the reservation indicated in the RESV message.

Note that it is possible to invoke traffic control without RSVP signaling, and to programmatically modify traffic control's treatment of a flow. RSVP signaling can be suppressed on a given flow if the SERVICE_NO_QOS_SIGNALING service type is specified, and traffic control can be suppressed on a given flow if the SERVICE_NO_TRAFFIC_CONTROL service type is specified. Additional control over the suppressing of RSVP signaling and traffic control can be achieved through the use of registry entries.

 

 

Community Additions

ADD
Show:
© 2015 Microsoft