> All this is really just pigeon dancing around the fact that Linux
> doesn't implement the PTHREAD_SCOPE_PROCESS which is all I want . I t
> would make Linux match Solaris and BSD model for POSIX threads. I guess
> it wouldn't be POSIX if everyone implemented it the same set of
> supported features. That's why I resorted to changing the nice value in
> hopes of have some say in how things get scheduled without all the
> superuser / capabilities hacks.
I just did a "man 3 pthreads" and that capability is listed as
available... If you can boil it down to a small test program as I did,
I'll run it on Linux and Solaris and see what I see.
Of course Linux doesn't implement anything here, you choose the
implementation by pthreads lib and includes, the old MIT user-level one,
the so-called "Linux threads" model, or the current NGPT model in current
kernels and the library from IBM.
The latter work, at least for some definitions of "work," but I know
there are some differences.
I don't see why starting two threads at different priorities when the
program does init is enough overhead to notice, but I don't have your
program so you may need something inobvious.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/