Running Timer Code - Revision history

Tmcnulty: update instructions -- toby & alex

2006-02-21T10:43:15Z

update instructions -- toby & alex

← Older revision		Revision as of 10:43, 21 February 2006
Line 3:		Line 3:

	===Setup a client and server with the tp_timer kernel===		===Setup a client and server with the tp_timer kernel===
	If you already have a client and server running the proper kernel, skip to the [[#Check_out_and_run_the_test_script\|next section]]. tp_timer should be compiled in module format (simply copy the -mod config below, as indicated).

	'''1. Build and install the kernel.'''		'''1. Build and install the kernel.'''
	To compile the kernel, check out <code>llk-sources</code> from CVS and use a .config file from llk-sources/ccg-configs. Make sure that <code>CONFIG_TP_TIMER=y</code> (for tp_timer built in) or <code>CONFIG_TP_TIMER=m</code> (for a module version of tp_timer). Note that there is a significant chance that this compilation will crash the build host is running tp_timer (having the module unloaded is okay). This is probably a problem with NFS, so building it locally may work (but watch out for distcc and ccache that like to touch files in your home directory). In short, build on a machine that isn't running a tp_timer kernel.		To compile the kernel, check out <code>llk-sources</code> from CVS and use a .config file from llk-sources/ccg-configs. Make sure that <code>CONFIG_TP_TIMER=y</code> (for tp_timer built in) or <code>CONFIG_TP_TIMER=m</code> (for a module version of tp_timer). Note that there is a significant chance that this compilation will crash the build host is running tp_timer (having the module unloaded is okay). This is probably a problem with NFS, so building it locally may work (but watch out for distcc and ccache that like to touch files in your home directory). In short, build on a machine that isn't running a tp_timer kernel.

			You probably want the module config (<code><machine>-mod</code> below). The resulting kernel version will be '2.6.9-llk-mod.' After building, <code>./ikl.py</code> in llk-sources will install the kernel locally for you. 2.6.9-llk-mod is the default kernel for both grub (on bazaar) and yaboot
			(on cairo).

	<pre>		<pre>
	cvs co llk-sources		cvs co llk-sources
			cvs co llk
	cd llk-sources		cd llk-sources
	cp ccg-configs/<machine>-mod .config # where machine is 'cairo' or 'bazaar'		cp ccg-configs/<machine>-mod .config # where machine is 'cairo' or 'bazaar'
Line 17:		Line 20:
	</pre>		</pre>

	'''2. ~~Setup~~ the boot-loader'''		'''2. Copy to another machine.'''
			If you need to copy the kernel to another machine, run:
			<pre>
			llk/scripts/distribute.sh 2.6.9-llk-mod <host name>
			</pre>

			'''3. Manage your kernels.'''
			We will probably accumulate a large number of kernels over the next couple days. These scripts will aid in managing that proliferation:
			*<code>llk/scripts/kernel_store.sh</code> saves the currently running kernel binary + associated files to a local directory (default: /usr/local/kernels/<kernel name specified>).
			*<code>llk/scripts/kernel_load.sh</code> restores one of the previously saved kernels to /boot (under the name of the currently running kernel).

			'''Boot-loader info,''' incase it's needed (you shouldn't have to change this!):
	<pre>		<pre>
	# on cairo:		# on cairo:
Line 27:		Line 41:
	grub < /etc/grub.conf		grub < /etc/grub.conf
	</pre>		</pre>

	~~'''3. Reboot.'''~~
	~~<pre>~~
	~~reboot~~
	~~</pre>~~

	===Check out and run the test script===		===Check out and run the test script===
	This must be done on a non-testing node, e.g., hopper. If you run this on a node you're using to test and accidently touch NFS, the machine will crash.		This must be done on a non-testing node, e.g., hopper. If you run this on a node you're using to test and accidently touch NFS, the machine will crash.

Tmcnulty at 06:38, 22 November 2005

2005-11-22T06:38:39Z

← Older revision		Revision as of 06:38, 22 November 2005
Line 6:		Line 6:

	'''1. Build and install the kernel.'''		'''1. Build and install the kernel.'''
			To compile the kernel, check out <code>llk-sources</code> from CVS and use a .config file from llk-sources/ccg-configs. Make sure that <code>CONFIG_TP_TIMER=y</code> (for tp_timer built in) or <code>CONFIG_TP_TIMER=m</code> (for a module version of tp_timer). Note that there is a significant chance that this compilation will crash the build host is running tp_timer (having the module unloaded is okay). This is probably a problem with NFS, so building it locally may work (but watch out for distcc and ccache that like to touch files in your home directory). In short, build on a machine that isn't running a tp_timer kernel.

	<pre>		<pre>
	cvs co llk-sources		cvs co llk-sources
Line 48:		Line 50:
	#load data from the log files into database		#load data from the log files into database
	#look at data via php scripts		#look at data via php scripts


	Machines setup with llk timing: b10,b11,c10,c11		Machines setup with llk timing: b10,b11,c10,c11
Line 54:		Line 55:
	Need to check out from CVS:		Need to check out from CVS:
	* llk-pacgen - cvs module with modified pacgen		* llk-pacgen - cvs module with modified pacgen



	To compile the kernel copy in a .config file from the ccg-configs cvs. Make sure that CONFIG_TP_TIMER=y (for tp_timer built in) or CONFIG_TP_TIMER=m (for a module version of tp_timer). And, checkout llk-sources. Note that there is a significant chance that this compilation will crash the machine running tp_timer (having the module unloaded is OK). This is probably a problem with NFS so building it locally may work. Otherwise, you may not want to compile the module on the machine you want to test with. Next, use standard machine dependent kernel build and install instructions:<br>
	~~<tt>make; make modules_install</tt><br>~~
	Copy the results of this to the target machine if it is not the local machine. Update, grub or yaboot, build initrd if that is needed, and reboot. If you have loaded it as a module you must <tt>modprobe tp_timer</tt> after boot in order to install the module. The first some number of packets from pacgen will be used to calibrate the timers. They should not be used for data.

	pacgen sample commands:		pacgen sample commands:

Tmcnulty: /* Obtaining Kernel Timing Data */

2005-11-22T06:27:34Z

Obtaining Kernel Timing Data

← Older revision		Revision as of 06:27, 22 November 2005
Line 11:		Line 11:
	cp ccg-configs/<machine>-mod .config # where machine is 'cairo' or 'bazaar'		cp ccg-configs/<machine>-mod .config # where machine is 'cairo' or 'bazaar'
	make oldconfig		make oldconfig
	make -jN CC="ccache gcc"		make -jN CC="ccache gcc" # where N is the number of hosts in DISTCC_HOSTS * 4
	./ikl.py # ikl = install kernel locally		./ikl.py # ikl = install kernel locally
	</pre>		</pre>

Tmcnulty: /* Check out and run the test script */

2005-11-22T06:26:25Z

Check out and run the test script

← Older revision		Revision as of 06:26, 22 November 2005
Line 38:		Line 38:
	./run_test.sh <client> <server> <protocol> <table name> <test set>		./run_test.sh <client> <server> <protocol> <table name> <test set>
	</pre>		</pre>
	Where <code><client></code> and <code><server></code> are short host names like '<code>b10</code>' and the protocol is '<code>udp</code>' or '<code>tcp</code>'.		Where <code><client></code> and <code><server></code> are short host names like '<code>b10</code>' and the protocol is '<code>udp</code>' or '<code>tcp</code>'. The script will load the module on both hosts, calibrate the test, run the test, fetch the data, unload the module, and insert the data into the database with the specified table name and test set label.

	==Older info==		==Older info==

Tmcnulty: /* Obtaining Kernel Timing Data */

2005-11-22T06:24:34Z

Obtaining Kernel Timing Data

← Older revision		Revision as of 06:24, 22 November 2005
Line 3:		Line 3:

	===Setup a client and server with the tp_timer kernel===		===Setup a client and server with the tp_timer kernel===
	If you already have a client and server running the proper kernel, skip to the[[#Check_out_and_run_the_test_script\|next section]]. tp_timer should be compiled in module format (simply copy the -mod config below, as indicated).		If you already have a client and server running the proper kernel, skip to the [[#Check_out_and_run_the_test_script\|next section]]. tp_timer should be compiled in module format (simply copy the -mod config below, as indicated).

	'''1. Build and install the kernel.'''		'''1. Build and install the kernel.'''

Tmcnulty: /* Obtaining Kernel Timing Data */

2005-11-22T06:24:19Z

Obtaining Kernel Timing Data

← Older revision		Revision as of 06:24, 22 November 2005
Line 3:		Line 3:

	===Setup a client and server with the tp_timer kernel===		===Setup a client and server with the tp_timer kernel===
	tp_timer should be compiled in module format (simply copy the -mod config below, as indicated).		If you already have a client and server running the proper kernel, skip to the[[#Check_out_and_run_the_test_script\|next section]]. tp_timer should be compiled in module format (simply copy the -mod config below, as indicated).

	'''1. Build and install the kernel.'''		'''1. Build and install the kernel.'''

Tmcnulty: /* Using run_test.sh */

2005-11-22T06:22:08Z

Using run_test.sh

← Older revision		Revision as of 06:22, 22 November 2005
Line 1:		Line 1:
	==~~Using run_test.sh~~==		==Obtaining Kernel Timing Data==
	Testing is now radically simplified with the <code>run_test.sh</code> script. ~~To execute the test, first setup~~ a client and server with a kernel ~~that includes~~ tp_timer in module ~~form:~~		Testing is now radically simplified with the <code>run_test.sh</code> script.

			===Setup a client and server with the tp_timer kernel===
			tp_timer should be compiled in module format (simply copy the -mod config below, as indicated).

	'''1. Build and install the kernel.'''		'''1. Build and install the kernel.'''

Tmcnulty: /* Using run_test.sh */

2005-11-22T06:19:08Z

Using run_test.sh

@@ Line 1: / Line 1: @@
 ==Using run_test.sh==
 <pre>
 cvs co llk
 cd llk/scripts
 ./run_test.sh <client> <server> <protocol> <table name> <test set>
 </pre>
-Where <code><client></code> and <code><server></code> are short host names like 'b10', the protocol is 'udp' or 'tcp'.
+Where <code><client></code> and <code><server></code> are short host names like '<code>b10</code>' and the protocol is '<code>udp</code>' or '<code>tcp</code>'.
 ==Older info==

Tmcnulty: add run_test.sh info

2005-11-22T06:11:16Z

add run_test.sh info

← Older revision		Revision as of 06:11, 22 November 2005
Line 1:		Line 1:
			==Using run_test.sh==
			<pre>
			# on a non-testing node, e.g., hopper (IMPORTANT!)
			cvs co llk
			cd llk/scripts
			./run_test.sh <client> <server> <protocol> <table name> <test set>
			</pre>
			Where <code><client></code> and <code><server></code> are short host names like 'b10', the protocol is 'udp' or 'tcp'.

			==Older info==
	Basic Flow:		Basic Flow:
	#make sure the tp_timer module is installed and working on the client and server nodes		#make sure the tp_timer module is installed and working on the client and server nodes

Lemanal at 00:22, 24 October 2005

2005-10-24T00:22:10Z

← Older revision		Revision as of 00:22, 24 October 2005
Line 17:		Line 17:
	To compile the kernel copy in a .config file from the ccg-configs cvs. Make sure that CONFIG_TP_TIMER=y (for tp_timer built in) or CONFIG_TP_TIMER=m (for a module version of tp_timer). And, checkout llk-sources. Note that there is a significant chance that this compilation will crash the machine running tp_timer (having the module unloaded is OK). This is probably a problem with NFS so building it locally may work. Otherwise, you may not want to compile the module on the machine you want to test with. Next, use standard machine dependent kernel build and install instructions:<br>		To compile the kernel copy in a .config file from the ccg-configs cvs. Make sure that CONFIG_TP_TIMER=y (for tp_timer built in) or CONFIG_TP_TIMER=m (for a module version of tp_timer). And, checkout llk-sources. Note that there is a significant chance that this compilation will crash the machine running tp_timer (having the module unloaded is OK). This is probably a problem with NFS so building it locally may work. Otherwise, you may not want to compile the module on the machine you want to test with. Next, use standard machine dependent kernel build and install instructions:<br>
	<tt>make; make modules_install</tt><br>		<tt>make; make modules_install</tt><br>
	Copy the results of this to the target machine if it is not the local machine. Update, grub or yaboot, build initrd if that is needed, and reboot. If you have loaded it as a module you must modprobe tp_timer after boot in order to install the module. The first some number of packets from pacgen will be used to calibrate the timers. They should not be used for data.		Copy the results of this to the target machine if it is not the local machine. Update, grub or yaboot, build initrd if that is needed, and reboot. If you have loaded it as a module you must <tt>modprobe tp_timer</tt> after boot in order to install the module. The first some number of packets from pacgen will be used to calibrate the timers. They should not be used for data.

	pacgen sample commands:		pacgen sample commands: