PM/Shmem Test Procedure

This test procedure assumes that the X window system is already running on the server. All commands must be invoked on the server host.
  1. Initialization test
    Issue the following commands: 
    $ cd /opt/score/sbin
$ ./rpminit comp0 shmem0
	Success: Nothing is printed
	Failure: Error and dump messages are printed
    If this test fails, please read the Troubleshooting section.

  2. Loopback test
    Issue the following commands: 
    $ cd /opt/score/sbin
$ ./rpmtest comp0 shmem0 -dest 0 -ping
	Success: Two numbers similar to "8     1.2269e-05" are printed
                 The first number is the data size (in bytes)
                 The second number is the latency (in seconds)
	Failure: Error and dump messages are printed
    If this test fails, please read the Troubleshooting section.

  3. Point-to-Point test (Message)
    Make sure that the PM Shmem driver is installed on the host. Issue the following commands: 
    $ cd /opt/score/sbin
$ ./rpmtest comp0 shmem1 -reply
    Issue the following commands in another window on the server host: 
    $ cd /opt/score/sbin
$ ./rpmtest comp0 shmem0 -dest 1 -ping
	Results should be the same as the loopback test
    When the test finishes, do not forget to kill the first pmtest process because it is in an infinite loop.
    If this test fails, read the Troubleshooting section.

  4. Point-to-Point test (Zero Copy)
    Issue the following commands: 
    $ cd /opt/score/sbin
$ ./rpmtest comp0 shmem1 -vreply
    Issue the following commands in another window on the server host: 
    $ cd /opt/score/sbin
$ ./rpmtest comp0 shmem0 -dest 1 -vread
	Results should be the same as the loopback test
    When the test finishes, do not forget to kill the pmtest process because the it is in an infinite loop.
    If this test fails, please read the Troubleshooting section.

Troubleshooting

Initialization test fails.
Loop back test fails.
Point-to-point test fails.
$Id: pm-testshmem.html,v 1.1.1.1 2002/02/12 02:00:13 kameyama Exp $