BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
When muxDevLoad( ) loads your driver, it calls muxDevStart( ), which then calls
your driver’s endStart( ) entry point.
H.2.2 Your ISR Puts Work on the Network Job Queue
Upon arrival of an interrupt on the network device, VxWorks invokes your
driver’s previously registered interrupt service routine. Your interrupt service
routine should do the minimum amount of work necessary to get the packet off the
local hardware. To minimize interrupt lock-out time, your interrupt service routine
should handle only those tasks that require minimal execution time, such as error
or status change. Your interrupt service routine should queue all time-consuming
work for processing at the task level.
To queue packet-reception work for processing at the task level, your interrupt
service routine must call netJobAdd( ). As input, this routine accepts a function
pointer and up to five additional arguments (parameters to the function referenced
by the function pointer).
STATUS netJobAdd
(
FUNCPTR routine, /* routine to add to netTask work queue */
int param1, /* first arg to added routine */
int param2, /* second arg to added routine */
int param3, /* third arg to added routine */
int param4, /* fourth arg to added routine */
int param5 /* fifth arg to added routine */
)
In your call to netJobAdd( ), you should specify your driver’s entry point for
processing packets at the task level. The netJobAdd( ) routine then puts the
function call (and arguments) on tNetTask’s work queue. VxWorks uses tNetTask
to handle task-level network processing.
NOTE: You can use netJobAdd( ) to queue up work other than processing for
received packets.
! CAUTION: Use netJobAdd( ) sparingly. The netJobRing is a finite resource that is
also used by the network stack. If it overflows, this implies a general network stack
corruption.
272