diff options
author | cdgill <cdgill@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 1998-10-19 03:24:48 +0000 |
---|---|---|
committer | cdgill <cdgill@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 1998-10-19 03:24:48 +0000 |
commit | 3bdedbbc8133b3628b02187d6539260d8bd8a65f (patch) | |
tree | c1239013b4c3806d4247e72db122b304d1f33e34 /TAO/orbsvcs/tests/Sched_Conf/README | |
parent | 40ffb7be7cf2cfdb393fcc99ee0a62d947dccf2c (diff) | |
download | ATCD-3bdedbbc8133b3628b02187d6539260d8bd8a65f.tar.gz |
Now propagating unresolved remote dependency warnings, added ability to generate schedule table even with warnings
Diffstat (limited to 'TAO/orbsvcs/tests/Sched_Conf/README')
-rw-r--r-- | TAO/orbsvcs/tests/Sched_Conf/README | 42 |
1 files changed, 42 insertions, 0 deletions
diff --git a/TAO/orbsvcs/tests/Sched_Conf/README b/TAO/orbsvcs/tests/Sched_Conf/README new file mode 100644 index 00000000000..e787e7d690a --- /dev/null +++ b/TAO/orbsvcs/tests/Sched_Conf/README @@ -0,0 +1,42 @@ +Overview: + + The scheduling service can run in one of two different modes of + operation, an off-line configuration mode, and a run-time execution mode. + The application uses the Scheduler_Factory to specify in which mode + it would like to use the scheduling service. + + In the configuration mode, the application registers RT_Infos containing + operation characteristics with the off-line scheduler, and also specifies + operation dependencies. The Event Channel also registers RT_Infos for its + own operations, and specifies any additional dependencies introduced by + subscription or event correllation. + + Once all operations are registered, the application invokes the + scheduler's compute_scheduling method. The scheduler generates a + "schedule" consisting of operation priorities and sub-priorities, and + determines whether or not the schedule is feasible. The scheduler also + produces queue specification information that can be used to configure + the dispatching module's number and kinds of queues (this + automatic dispatching module configuration will appear in a TAO release + *very* soon). The application then may ask the config scheduler to dump + it's schedule to a header file. + + The Sched_Conf.cpp file in this directory is an example of how this is done. + Building and running the Sched_Conf executable will produce a header file + called Sched_Conf_Runtime.h, which is included by Sched_Conf_Runtime.cpp. + + The dumped header file contains tables with the static scheduling and + configuration information. The Sched_Conf_Runtime application passes this + information to the run-time scheduler at start-up. The application may also + re-register its operations to verify the correct operations were loaded. The + Sched_Conf_Runtime does this, and in fact exercises a number of methods + of the run-time scheduler to ensure it gives correct responses for the + table of operations with which it was instantiated. + +Program operation: + + build Sched_Conf + run Sched_Conf + build Sched_Conf_Runtime + run Sched_Conf_Runtime + |