README file for SMLPLAN-P

There are two executables:

These can be tested as follows:

These tests simulate a machine with two interfaces (as indicated by the file astero1.cfg). The movie is received at one interface, and a client is subscribed at the other interface. The third argument interface_load is the load at this outgoing interface. For the mpeg_sml.pp program, values within the following ranges have the following effects:

0-1700000: drop nothing
1700001-1900000: drop B frames
1900001-2000000: drop P frames

Sample output is as follows:

% spec mpeg_sml.pp astero1 1750000
No. of variables: 52
Stack size: 5
Heap size: 768
8:0:20:89:56:b6 on hme1 (interface 1)
0:c0:4f:72:f0:76 on hme1 (interface 1)
0:c0:4f:72:f0:9 on hme1 (interface 1)
8:0:20:b0:91:e5 on hme1 (interface 1)
8:0:20:9f:5c:90 on hme0 (interface 0)
1: 5373434 / 500 = 10746
2: 34042 / 2 = 17021
The first three lines describe the estimated memory requirements of the PLAN-P program.

The next five lines print information about known hosts and interfaces, based on the file astero1.cfg.

The next line prints the total and average treatment times for each of the 500 packets of movie data in astero1.

The last line prints the total and average treatment times for the two signalling packets: one from the server to install the movie, and one from the client to subscribe to the movie.

Times are in nanoseconds and obtained using gethrtime.