This is the mail archive of the ecos-devel@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

PTHREAD_INHERIT_SCHED


POSIX threads default to having the PTHREAD_INHERIT_SCHED attribute. There's a problem though: it all fubars if the parent thread is an eCos thread, not a POSIX one.

Unfortunately the child thread can't tell what the parent is (and relying on magic numbers or somesuch is Bad). I notice from the man pages that Linux/glibc defaults to PTHREAD_EXPLICIT_SCHED. Any reason we shouldn't do the same?

I ask because it it's a not insignificant change in semantics.

Jifl
--
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]