Re: Thread behaviour using pthread

From: "David Schwartz" <davids@xxxxxxxxxxxxx>
Date: Fri, 24 Mar 2006 15:51:14 -0800

"Igor" <igor_k70@xxxxxxxxxxx> wrote in message
news:e01713$dnh$1@xxxxxxxxxxxxxxxxxxxxxxxxx

I have tried using pthread library on Linux (2.6 kernel) and found that
setting parameters in the attr structure
do not seem to change anything in the thread behaviour - changing sched
policy (RR, FIFO) or RT priority. So, it seems that any changes to attr
structure for a thread are transparent. The only way I could change the
behaviour is by using process level calls like sched_setscheduler etc.on a
thread.

Is there anything I am missing?

Post minimal example code, you may be doing it wrong. It's not
particularly difficult, but there are a few gotchas.

DS

.

Follow-Ups:
- Re: Thread behaviour using pthread
  - From: Igor

References:
- Thread behaviour using pthread
  - From: Igor

Prev by Date: Re: Application Security Options--USB Dongle?
Next by Date: Inter-client communication with NET protocol
Previous by thread: Re: Thread behaviour using pthread
Next by thread: Re: Thread behaviour using pthread
Index(es):
- Date
- Thread

Relevant Pages

Re: Thread behaviour using pthread
... setting parameters in the attr structure ... do not seem to change anything in the thread behaviour - changing sched ... otherwise the thread created inherits the schedpolicy and schedparam ...
(comp.os.linux.development.apps)
Thread behaviour using pthread
... I have tried using pthread library on Linux (2.6 kernel) and found that ... setting parameters in the attr structure ... do not seem to change anything in the thread behaviour - changing sched ...
(comp.os.linux.development.apps)