Linked by Thom Holwerda on Sat 7th Feb 2009 00:35 UTC, submitted by PlatformAgnostic
Windows M:N threading, in which a single kernel thread is multiplexed to run multiple logical user mode threads, has long been a feature of some Unix systems (Solaris and FreeBSD have had it for years). Even Windows NT has had "Fibers" for several releases, though they suffered from the same problems as other M:N schemes and were incompatible with many Win32 APIs. Join Windows Kernel Architect Dave Probert for a discussion on the new User Mode Scheduling Feature which solves these problems while allowing applications fine grained control over their threads.
Permalink for comment 348277
To read all comments associated with this story, please click here.
Bill Shooter of Bul
Member since:

Do you have to really program specifically for M:N, or does the operating system just take your thread creation requests and treat them as these fibers? I would think that M:N would only make sense if the application were creating a large number of threads in multiple programs. Otherwise there are two levels of scheduling overhead. If the server is single purposed, it should only have one of those. Of course on desktops and servers that have a more varied load, it might make some sense.

Edited 2009-02-11 16:06 UTC

Reply Parent Score: 1