On Sun, Jan 16, 2005 at 05:57:23PM -0600, Jack O'Quin wrote: > > * Jack O'Quin <[EMAIL PROTECTED]> wrote: > >> According to the manpage, nice(2) is per-process not per-thread. That > >> does not give the granularity we need. > > Ingo Molnar <[EMAIL PROTECTED]> writes: > > the manpage is incorrect - sys_nice() is per-thread. (Btw., you could > > use setpriority() too.) > > OK. Where is this stuff documented? > > BTW, I think this violates POSIX, which states... > > The nice value set with nice() shall be applied to the process. If > the process is multi-threaded, the nice value shall affect all > system scope threads in the process.
We are talking about two different things here. POSIX is just about API and has, correct me if I'm wrong, nothing to do with system calls whatsoever. The manpage nice(2) is about the libc library call nice(), which is per-process, which it should be according to POSIX. The system call, called sys_nice() in C, is per-thread. Apparently glibc or some thread library contains some magic to make the translation. Sytse - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
