* Roland Mainz <[EMAIL PROTECTED]> [2008-06-09 10:23]:
> In this example the application launches threads... and by "accident"
> the author has set the limit to (Inf/1.) (=positive Infinite
> dividided by 1 is still infinite... ps... =:-) ) instead of a
> plain value like 64. In this ca
I suppose you could sort of emulate a per-process thread limit, within
the C code of the shell, so that a ulimit shell command would (mostly) work
as expected, although that might require the shell to do a settaskid() when
exec'd, and also when returning from fork() in the child, so that the scope
[...]
> I have noticed that the scheduler often throw around
> a thread among different processors. An improvement
> would be to make the thread stay at the processor it
> was first assigned to, but I don't know how to
> achieve this. I've heard about pbind, but to my
> understanding that only rest
Thanks for the input regarding P_MYID,
I was a bit puzzled at first using P_MYID because I got a '1' as a return
value, I sort of expected somthing like "2234112". But, now I understand that
it actually was the correct value.
I'll use this method in the future as it is cleaner than previous ap
