Linked by Eugenia Loli on Fri 4th Aug 2006 23:31 UTC, submitted by IdaAshley
Linux The LinuxThreads project originally brought multithreading to Linux, but didn't conform to POSIX threading standards. The introduction of Native POSIX Thread Library (NPTL) however, overcame many of these disadvantages. This article describes some of the differences between these two Linux threading models for developers who may need to port their applications or who simply want to understand where the differences lie.
Thread beginning with comment 149450
To read all comments associated with this story, please click here.
M:N is just too complicated
by abraxas on Sat 5th Aug 2006 23:46 UTC
Member since:

The problem with an M:N approach is that it is just too complicated. I prefer the KISS approach and it seems to work well when it comes to threading, at least for Linux. Userspace/Kernelspace synchronization becomes such a hassle with M:N that it is not even worth it.

I prefer NPTL over something like NGPT which had an M:N threading model. In fact NPTL beat the pants off of NGPT and that's why NPTL was chosen over NGPT. We have Ingo Molnar to thank for that as he was the one that improved Linux scheduling to the point that NPTL became more viable than an M:N approach like NGPT.

I have used NPTL for quite some time now but I experimented with NGPT at one time because it was available for Redhat. In my not so scientific experience NGPT could not keep up with NPTL and real benchmarks show the same.

Reply Score: 1