The workload attribute describes two fundamentally
different models of the work that the server has to manage.
The first model is the bounded workload, in which
the application can bound the amount of work that it
requests during an interval equal to the server’s period.
We call this work a job. In this model, it is possible for
an application to tell the system that it has completed
the current job (thus allowing the system to make its
current available budget equal to zero), and that it
should be awakened by the system at the beginning of
the next job. If requested, the system can notify the
application about a job overrunning its budget, or missing
its deadline. This is the preferred approach for periodic
of sporadic tasks running on top of an FSF server.
The notification can be addressed to a thread under the
server, or to a special-purpose handler thread, created
by the application.
The workload attribute describes two fundamentallydifferent models of the work that the server has to manage.The first model is the bounded workload, in whichthe application can bound the amount of work that itrequests during an interval equal to the server’s period.We call this work a job. In this model, it is possible foran application to tell the system that it has completedthe current job (thus allowing the system to make itscurrent available budget equal to zero), and that itshould be awakened by the system at the beginning ofthe next job. If requested, the system can notify theapplication about a job overrunning its budget, or missingits deadline. This is the preferred approach for periodicof sporadic tasks running on top of an FSF server.The notification can be addressed to a thread under theserver, or to a special-purpose handler thread, createdby the application.
การแปล กรุณารอสักครู่..