Jivin Michael Schnell lays it down ... > > > >I said uClinux, so specifically I mean non-MMU varieties of Linux. > Of course I do know the difference. I'm going to do an embedded > controller project. So I'm very likely to use µcLinux > > > > > >>As of 2.6 we have a Posix threads representation in the Kernel > >>(NPTL). This should have changed the behavior of threads. > > > >What architecture? > Supposedly NIOS. I do know that Altera is going to release an MMU for > that processor very soon, but that will reduce the performance by up at > least 10 % and while the 2.6.23 µCLinux for NIOS is just getting ready, > I suppose that there will be a while until a decent "full" Linux > distribution is available. > > Anyway: While I do see that and why why fork() is not available in > µCLinux and thus spawning a process is not as easily as it is in full > Linux, I can't see what problems are introduced regarding threads.
It's not uClinux specifically, I am fairly sure the black fin guys will tell us that threads work great for them. The problem is not so much uClinux, but how much time/testing and use that feature has had on the architecture in question. So for blackfin, they have focused heavily on their toolchain support and so on ensuring that C++ and threads and similar features are all solid, and it shows. Other arches have significant projects using C, but not so much in the C++ or threads space, and thus not much focus on bugs in those areas. This can mean you will run into bugs and glitches, all of which can be fixed, it's just that no one has spent the time doing it. Cheers, Davidm -- David McCullough, [EMAIL PROTECTED], Ph:+61 734352815 Secure Computing - SnapGear http://www.uCdot.org http://www.cyberguard.com _______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
