Scenarios and technologies of QOS2

re: Scenarios and technologies of QOS2

Dave Barratt — Wed, 23 Jan 2008 13:22:58 GMT

This is all very well but what if you write network stress testing applications and you just want to vary the diffserv byte in the ip header. Too much stuff to learn to do a simple thing! Is there no registry setting like XP to allow direct setting of the byte?

Xbox 360 Fall Update Includes LLTD

Windows Core Networking — Wed, 01 Nov 2006 10:37:10 GMT

There has been a lot of buzz about the recent fall update for the Xbox 360; however, an important new

re: Scenarios and technologies of QOS2

wndpteam — Wed, 02 Aug 2006 23:50:18 GMT

I'll definitely post a blog about Pacer and its role to clear up the confusion. Thanks for the feedback!
Pacer.sys is absolutely necessary for *any* QoS scenario in Windows, home or enterprise. Pacer is the Vista replacement for Psched.sys in earlier releases; implemented as an NDIS-6 light-weight filter (LWF) driver. Pacer does not do any classification, it's job is to maintain QoS flows and their characteristics. For example, When a flow is created via a QoS API (Qos2, TC, GQoS) or Group Policy based component, Pacer makes sure the send rate specified is honored and that the flow gets priority tags. Look for a post on this in the next few days.
- Gabe

re: Scenarios and technologies of QOS2

Pavel A. — Wed, 02 Aug 2006 23:35:08 GMT

Thank you Gabe, I'll need to look at the WFP and QOS2 API again...
From the first look I've gathered (wrongly?) that you implemented two different solutions:
Pacer is for business class managed clients, and it does classification, as previosly TC did. qWave and QOS2 is for unmanaged / self managed networks, and it lets the apps mark their traffic with priority. Then, some other layer can (optionally) shape traffic based on the flow characteristics - but there is no classification such as by port, ip protocol and so on. correct?

Adding QOS2 calls in a sample Winsock application - Part 1

Windows Network Development — Wed, 12 Jul 2006 21:21:49 GMT

Over the past few months we've been receiving feedback from partners on the new QOS2&nbsp;API I just...

Adding QOS2 calls in a sample Winsock application - Part 1

Windows Network Development — Wed, 12 Jul 2006 21:19:52 GMT

Over the past few months we've been receiving feedback from partners on the new QOS2&nbsp;API I just...

re: Scenarios and technologies of QOS2

wndpteam — Mon, 10 Jul 2006 10:44:08 GMT

Actually, Vista provides a full, comprehensive platform for classification called WFP (Windows Filtering Platform). Please review the WFP post category on this blog. Qos2 APIs take a socket handle as input, and as such, the QoS subsystem knows all the classification information necessary to match outgoing packets for the flow (src/dst IP address, src/dst port, and protocol). The hardware (or NIC driver) is not responsible in any way for classification.
That said, the OS does *both* classification and probing to estimate bandwidth real-time. If you are a little more specific with your question, I'd be happy to answer.
- Gabe

re: Scenarios and technologies of QOS2

PavelA — Sun, 09 Jul 2006 20:13:44 GMT

So, in Vista the OS no longer does any classification? It does only probing on L2+ layers and the classification got "offloaded" to the lower (hardware) transport layers?