Geek asks and answers

Linux / vxworks Signals

In the vxworks manual, I came across the following: I wonder why this is so.

What types of signals do what makes them undesirable?

In applications, signals are most suitable for error and exception processing, and not for general-purpose communication tasks.

+3
source share
1 answer

The main problem with signals is that signal handlers are registered on the basis of each process / memory (in vxWorks, the kernel represents one memory space, and each RTP is a different memory space).

, / ( ). , .

, , , , .

  Task A                       Task B               Signal Handler
  Take  Mutex
   ...
   Gets preempted 
                                does something
                                 ....
                                <SIGNAL ARRIVES>----->Take Mutex  (blocks)
   resumes
   ....
   Give Mutex
                                                ----->Resumes Handler

, , . :

  • , /. , , ,
  • , Task/Thread . / ( / ). VxWorks .

, , kill.

, .

+3

More articles:


All Articles