ioctl_vxWorks(国外英语资料).docVIP

ioctl_vxWorks(国外英语资料) VxWorks program guide (2010-06-11, 09:30) Category: VxWorks ******************************************* I. task ******************************************* Task status: hang up, block, ready, sleep. Tasks can be deleted in any of the states. There are 256 priorities in the Wind kernel, 0 highest and 255 lowest. Task scheduling control function KernelTimeSlice () control round robin scheduling TaskPrioritySet () change task priority TaskLock () prohibit task scheduling TaskUnlock () allows task scheduling When a task accesses a variable or data structure that might be interrupted by a service program, you can use intLock () to implement mutual exclusion. Preemptive locking by taskLock () and taskUnlock () prevents preemption of priority, and interrupt service routine can still be executed. The priority of all application tasks should be between 100-250; however, the task that the driver supports (the task associated with the interrupt service routine) can be located at 51-99. Spatial allocation of task stack: in order to avoid stack overflow and destruction of task stack, the following methods can be used: In the initial allocation of the stack space, a space larger than previously estimated is allocated; periodically, the checkStack () function is monitored; if the space is less secure, the size of the allocation space is modified. The general vxWorks uses the task ID number to locate the task, and specifies that the ID number is 0 to represent the task call. The vxWorks operating system does not need a unique task name, but it is recommended to use the unique task name in order to avoid confusion. The task naming rule of the vxWorks operating system: all tasks initiated from the target start with the letter t, while the task initiated from the host begins with the letter U. Task creation function TaskSpawn () creates and activates a new task TaskInit () initializes a new task TaskActivate () activates an initialization task Task name and ID fu