In QoS, you can specify the application's requirement for network service
quality. For example, the guaranteed service promises to carry a certain
traffic volume with a quantifiable bounded latency. The controlled load
service agrees to carry a certain traffic volume to a service level that
approximates what could be achieved when the network is lightly loaded. The
qualitative service indicates that the application requires better than
BESTEFFORT transmission, but cannot quantify its transmission requirements.
Applications that use the SERVICETYPE_QUALITATIVE service type should
supply an application ID policy element. The application ID policy element
enables policy servers on the network to identify the application and
assign an appropriate QOS to the application request by returning a DCLASS
object.
You can find more readings about this in the article Winsock 2: QoS API
Fine-Tunes Networked App Throughput and Reliability
http://msdn.microsoft.com/en-us/magazine/cc301862.aspx.
Regards,
Jialiang Ge
Microsoft Online Community Support
=================================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msd...@microsoft.com.
This posting is provided "AS IS" with no warranties, and confers no rights.
=================================================
I quote a few more information from the article
http://msdn.microsoft.com/en-us/magazine/cc301862.aspx for you:
GQoS allows a Winsock app to inform the network of its traffic
requirements. How those requirements are met depends on policies
established by network administrators. This means entitled users or apps
can receive preferential treatment for their net traffic.
So, a policy at the user or application level is not sufficient. Since the
protocols belong to the same application run by the same user.
Kind regards,
Mario
""Jialiang Ge [MSFT]"" <jia...@online.microsoft.com> wrote in message
news:ieT9aJ4j...@TK2MSFTNGHUB02.phx.gbl...
I'm still performing researches on this question. I will update you as soon
as I have any findings.
After perforing more researches, I got these information:
Windows will internally prioritize packets by their service type value iff
the number of packets pended to the NIC is >= the value of
MaxOutstandingSends
(http://technet.microsoft.com/en-us/library/cc758267(WS.10).aspx). The
default value of MaxOutstandingSends is 65536 so you will very rarely see
this in effect. Priority queues are emptied in a deficit round robin
fashion.
kind regards,
Mario
PS: I did implement an application level packet prioritizer for my
application, but this can never be made as efficient as a kernel
implementation.
""Jialiang Ge [MSFT]"" <jia...@online.microsoft.com> wrote in message
news:xh2BdENl...@TK2MSFTNGHUB02.phx.gbl...
After perforing many researches, I do not find another way to internally
prioritize my packets. Could limiting bandwidth help in this case?