Running Timer Code

Basic Flow:

1. clear /proc/tp_timer on both client and server machines (just read it's contents; cat /proc/tp_timer)
2. run pacgen on client and server to amass new data.
3. read data into log files on both server and client
4. load data from the log files into database

Machines setup with llk timing: b10,b11,c10,c11

Need to check out:

• llk-pacgen - cvs module with modified pacgen

tp timer must be compiled into the kernel or compiled/loaded as a module. Note that there is a significant chance that this compilation will crash the machine. May not want to compile the module on the machine you want to test with.

pacgen sample commands:

./server tcp <port number>
./client -t <protocol> -s <source IP> -m <source port> -d <dest IP> -p <dest port>

Each window is a specific ID for the packet. This ID is used as the payload for the packets. Useful for checking for packet fragmentation (educated guess via Alex). Windows are 0xffffffff, 0xffffffff (2 unsigned ints worth of 1's), an unsigned int for socket/thread id (We don't use it; that part of the code was removed), and an unsigned int holding the window number (we don't know what this is for).

After pacgen is ran with on a tp timer enabled machine, the timing results will be available in /proc/tp_timer. Note that after you read this proc entry, the information will be cleared.

Toby's instructions for clearing and loading the mysql database on hopper to use with the php timer analysis script:

mysql -uroot tp_timer

delete from serv_ts;
delete from cli_ts;
load data infile '/path/to/timing/server_data.log' into table serv_ts fields terminated by ', ';
load data infile '/path/to/timing/client_data.log' into table cli_ts fields terminated by ', ';