This is the mail archive of the ecos-discuss@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]

Re: Why to signal condvar with mutex held?

Sergei Organov <osv@topconrd.ru> writes:

> That's exactly what I fail to see, -- which realtime guarantee that is
> met in the first case isn't met in the second. Though let's don't focus
> on the issue too much as for me it's just a curiosity.

Mainly it's about avoiding priority inversion. 

> > The approach came from experience plus a desire to keep the kernel
> > mechanisms as simple as possible.
> 
> Are you aware of any other (RT)OS/thread library that uses similar
> technique?
>

Not offhand. I don't think it is particularly unusual, it's a design
choice that all OS designers need to make.

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]