ZeptoOS - User contributions [en]

MediaWiki:Sidebar

2009-05-11T22:04:24Z

Hnaik:

*
** mainpage|Top
** http://www.zeptoos.org|ZeptoOS Home
* SEARCH
* TOOLBOX
* LANGUAGES

MediaWiki:Sidebar

2009-04-22T21:03:21Z

Hnaik:

* Documentation Menu
** mainpage|Home
** http://www.mcs.anl.gov/research/projects/zeptoos/cms|ZeptoOS Home
* SEARCH
* TOOLBOX
* LANGUAGES

MediaWiki:Sidebar

2009-04-22T21:02:39Z

Hnaik:

* '''Doc Menu'''
** mainpage|Documentation Home
** http://www.mcs.anl.gov/research/projects/zeptoos/cms|ZeptoOS Home
* SEARCH
* TOOLBOX
* LANGUAGES

MediaWiki:Sidebar

2009-04-22T20:59:41Z

Hnaik:

* Menu
** mainpage|Documentation Home
** http://www.mcs.anl.gov/research/projects/zeptoos/cms|ZeptoOS Home
* SEARCH
* TOOLBOX
* LANGUAGES

Configuration

2009-04-22T20:53:53Z

Hnaik:

[[Introduction]] | [[ZeptoOS_Documentation|Top]] | [[Installation]]
----

== Checklist ==

* It is necessary that the user is logged on the the login node.

== Configuring the Build ==

=== The Configure Script ===
Download the bzipped file on the [[Blue Gene/P]] login node. Extract the sources by using:
<pre>$ tar xjf ZeptoOS-V20-V1R3M0-beta-20090401161133.tar.bz2 </pre>

Change to the BGP top directory using:
<pre>$ cd BGP/</pre>

Then you can use the ''configure'' script to set the system tools path to default using:
<pre>$ ./configure</pre>

In order to configure the site specific paths using the tool use:
<pre>$ ./configure --edit</pre>

== Building ZeptoOS V2.0 ==

Typing ''make help'' will bring up the following menu:
<pre>
[MENU]

make - Prepare Zepto kernel and ramdisk images

make bgp-ion-ramdisk - Rebuild ION ramdisk for CNK
make bgp-ion-ramdisk-cnl - Rebuild ION ramdisk for CNL

make bgp-ion-linux - Simply use recent built or prebuilt ION kernel (no kernel rebuild)
make bgp-cn-linux - Rebuild CN ramdisk and merge with recent built or prebuilt CN kernel objs

make bgp-ion-linux-build - Rebuild ION kernel
make bgp-cn-linux-build - Rebuild CN kernel objs and CN ramdisk, then merge them into CN Kernel

make bgp-all-pkg-smart - Build packages from the prebuilt binaries
make bgp-all-pkg-rebuild - Rebuild all packages from source
</pre>

To start using the default built binaries simply type:
<pre>$ make</pre>
This will copy all the required kernel and ramdisk images to the top level directory.

=== Examining the Build Directory ===
If the build was successful, one should be able to see the following new files either rebuilt from sources or copied from their prebuilt locations:
<pre>
$ ls -l
-rwxr-xr-x 1 hnaik users 8629983 2009-01-23 17:16 BGP-CN-zImage-with-initrd.elf
-rwxr-xr-x 1 hnaik users 1444183 2009-01-23 17:03 BGP-exp-ION-zImage.elf
-rwxr-xr-x 1 hnaik users 10423112 2009-01-23 17:03 BGP-ION-ramdisk.elf
-rwxr-xr-x 1 hnaik users 10423988 2009-01-23 17:03 BGP-ION-ramdisk-for-CNL.elf
-rw-r--r-- 1 hnaik users 132 2009-01-23 17:03 bgp-ion-ramdisk-passwd.txt
-rwxr-xr-x 1 hnaik users 1351583 2009-01-23 17:08 BGP-ION-zImage.elf
</pre>

----
[[Introduction]] | [[ZeptoOS_Documentation|Top]] | [[Installation]]

Introduction

2009-04-22T20:53:00Z

Hnaik:

[[ZeptoOS_Documentation|Top]] | [[The Build Process]]
----

ZeptoOS is a research project investigating operating systems and run-time systems and libraries for petascale architectures with 10,000 to 1 million CPUs. The ZeptoOS project is a collaboration between Argonne National Laboratory and the University of Oregon.

For IBM's Bluegene/P platform, we are investigating highly efficient Linux-based compute node and I/O node kernels and advanced-functionality libraries and tools that support efficient collective operations, parallel I/O, and performance monitoring tools. Most of the time, to accomplish our Computer Science research goals we must replace IBM's closed-source components with Open Source versions that we have either written from scratch or adapted from other Open Source pieces. The new components are fast, small, reliable, infinitely flexible, and with lots of new features.

----
[[ZeptoOS_Documentation|Top]] | [[The Build Process]]

Introduction

2009-04-22T20:52:13Z

Hnaik:

[[ZeptoOS_Documentation|Top]] | [[Features]]
----

ZeptoOS is a research project investigating operating systems and run-time systems and libraries for petascale architectures with 10,000 to 1 million CPUs. The ZeptoOS project is a collaboration between Argonne National Laboratory and the University of Oregon.

For IBM's Bluegene/P platform, we are investigating highly efficient Linux-based compute node and I/O node kernels and advanced-functionality libraries and tools that support efficient collective operations, parallel I/O, and performance monitoring tools. Most of the time, to accomplish our Computer Science research goals we must replace IBM's closed-source components with Open Source versions that we have either written from scratch or adapted from other Open Source pieces. The new components are fast, small, reliable, infinitely flexible, and with lots of new features.

----
[[ZeptoOS_Documentation|Top]] | [[Features]]

Configuration

2009-04-22T20:51:41Z

Hnaik:

[[Features]] | [[ZeptoOS_Documentation|Top]] | [[Installation]]
----

== Checklist ==

* It is necessary that the user is logged on the the login node.

== Configuring the Build ==

=== The Configure Script ===
Download the bzipped file on the [[Blue Gene/P]] login node. Extract the sources by using:
<pre>$ tar xjf ZeptoOS-V20-V1R3M0-beta-20090401161133.tar.bz2 </pre>

Change to the BGP top directory using:
<pre>$ cd BGP/</pre>

Then you can use the ''configure'' script to set the system tools path to default using:
<pre>$ ./configure</pre>

In order to configure the site specific paths using the tool use:
<pre>$ ./configure --edit</pre>

== Building ZeptoOS V2.0 ==

Typing ''make help'' will bring up the following menu:
<pre>
[MENU]

make - Prepare Zepto kernel and ramdisk images

make bgp-ion-ramdisk - Rebuild ION ramdisk for CNK
make bgp-ion-ramdisk-cnl - Rebuild ION ramdisk for CNL

make bgp-ion-linux - Simply use recent built or prebuilt ION kernel (no kernel rebuild)
make bgp-cn-linux - Rebuild CN ramdisk and merge with recent built or prebuilt CN kernel objs

make bgp-ion-linux-build - Rebuild ION kernel
make bgp-cn-linux-build - Rebuild CN kernel objs and CN ramdisk, then merge them into CN Kernel

make bgp-all-pkg-smart - Build packages from the prebuilt binaries
make bgp-all-pkg-rebuild - Rebuild all packages from source
</pre>

To start using the default built binaries simply type:
<pre>$ make</pre>
This will copy all the required kernel and ramdisk images to the top level directory.

=== Examining the Build Directory ===
If the build was successful, one should be able to see the following new files either rebuilt from sources or copied from their prebuilt locations:
<pre>
$ ls -l
-rwxr-xr-x 1 hnaik users 8629983 2009-01-23 17:16 BGP-CN-zImage-with-initrd.elf
-rwxr-xr-x 1 hnaik users 1444183 2009-01-23 17:03 BGP-exp-ION-zImage.elf
-rwxr-xr-x 1 hnaik users 10423112 2009-01-23 17:03 BGP-ION-ramdisk.elf
-rwxr-xr-x 1 hnaik users 10423988 2009-01-23 17:03 BGP-ION-ramdisk-for-CNL.elf
-rw-r--r-- 1 hnaik users 132 2009-01-23 17:03 bgp-ion-ramdisk-passwd.txt
-rwxr-xr-x 1 hnaik users 1351583 2009-01-23 17:08 BGP-ION-zImage.elf
</pre>

----
[[Features]] | [[ZeptoOS_Documentation|Top]] | [[Installation]]

Installation old

2009-04-22T20:51:19Z

Hnaik:

[[The Build Process]] | [[ZeptoOS_Documentation|Top]] | [[Testing]]
----
In order to install the headers, libraries and the binaries, just type:
<pre>
$ python install.py /path/to/install
</pre>

This will install the following files:
<pre>
Install Home: /path/to/install
Creating install directories ...
Making /path/to/install/bin
Making /path/to/install/include
Making /path/to/install/lib

Installing mpich2 scripts ...
Installing /path/to/install/bin/zmpicc
Installing /path/to/install/bin/zmpicxx
Installing /path/to/install/bin/zmpif77
Installing /path/to/install/bin/zmpif90
Installing /path/to/install/bin/zmpixlc_r
Installing /path/to/install/bin/zmpixlc
Installing /path/to/install/bin/zmpixlcxx_r
Installing /path/to/install/bin/zmpixlcxx
Installing /path/to/install/bin/zmpixlf2003_r
Installing /path/to/install/bin/zmpixlf2003
Installing /path/to/install/bin/zmpixlf77_r
Installing /path/to/install/bin/zmpixlf77
Installing /path/to/install/bin/zmpixlf90_r
Installing /path/to/install/bin/zmpixlf90
Installing /path/to/install/bin/zmpixlf95_r
Installing /path/to/install/bin/zmpixlf95

Installing misc files ...
/path/to/install/bin/zelftool

Installing MPICH2 headers ...
/path/to/install/include/mpe_thread.h
/path/to/install/include/mpi_base.mod
/path/to/install/include/mpi_constants.mod
/path/to/install/include/mpicxx.h
/path/to/install/include/mpif.h
/path/to/install/include/mpi.h
/path/to/install/include/mpi.mod
/path/to/install/include/mpiof.h
/path/to/install/include/mpio.h
/path/to/install/include/mpi_sizeofs.mod
/path/to/install/include/mpix.h

Installing MPICH2 libraries ...
/path/to/install/lib/libcxxmpich.zcl.a
/path/to/install/lib/libfmpich_.zcl.a
/path/to/install/lib/libfmpich.zcl.a
/path/to/install/lib/libmpich.zcl.a
/path/to/install/lib/libmpich.zclf90.a

Installing SPI libraries ...
/path/to/install/lib/libSPI.zcl.a
/path/to/install/lib/libzcl.a

Installing Zoid files ...
/path/to/install/lib/libzoid_cn.a

Installing DCMF files ...
/path/to/install/include/dcmf_collectives.h
/path/to/install/include/dcmf_coremath.h
/path/to/install/include/dcmf_globalcollectives.h
/path/to/install/include/dcmf.h
/path/to/install/include/dcmf_multisend.h
/path/to/install/include/dcmf_optimath.h
/path/to/install/lib/libdcmfcoll.zcl.a
/path/to/install/lib/libdcmf.zcl.a
</pre>

== Kernel & Ramdisk ==

----
[[The Build Process]] | [[ZeptoOS_Documentation|Top]] | [[Testing]]

Testing

2009-04-22T20:51:00Z

Hnaik:

[[Installation]] | [[ZeptoOS_Documentation|Top]] | [[The ZeptoOS V2.0 Kernel]]
----

== Using Testcode ==
Once the files installations have been done and the profiles defined by creating symbolic links to the images in the top-level directory, it is time to submit a test job. Use the test program provided with the distribution. From the top level directory:
<pre>
$ cd comm/testcodes
</pre>

=== Compiling ===

The program can be compiled on the login node using:
<pre>
$ /path/to/install/bin/zmpicc -o mpi-test-linux mpi-test.c
$ /path/to/install/bin/zmpixlc_r -openmp -o omp-test-linux omp-test.c
</pre>

=== Submitting Job ===
(For ANL Users)
The job needs to be submitted using the [[cobalt]] resource manager. For the ''mpi-test'' program use the following command:
<pre>
cqsub -n <number-of-processes> -t <time> -k <profile-name> mpi-test-linux
cqsub -n <number-of-processes> -t <time> -k <profile-name> -e OMP_NUM_THREADS=<num> omp-test-linux
</pre>

----
[[Installation]] | [[ZeptoOS_Documentation|Top]] | [[The ZeptoOS V2.0 Kernel]]

The ZeptoOS V2.0 Kernel

2009-04-22T20:50:39Z

Hnaik:

The ZeptoOS Ramdisk

2009-04-22T20:50:17Z

Hnaik:

Other Packages

2009-04-22T20:50:01Z

Hnaik:

ZOID

2009-04-22T20:49:46Z

Hnaik:

(K)TAU

2009-04-22T20:49:27Z

Hnaik:

[[Zoid]] | [[ZeptoOS_Documentation|Top]] | [[FAQ]]
----

----
[[Zoid]] | [[ZeptoOS_Documentation|Top]] | [[FAQ]]

(K)TAU

2009-04-22T20:48:58Z

Hnaik:

[[Zoid]] | [[ZeptoOS_Documentation|Top]] [[FAQ]]
----

----
[[Zoid]] | [[ZeptoOS_Documentation|Top]] [[FAQ]]

FAQ

2009-04-22T20:48:46Z

Hnaik:

[[KTAU]] | [[ZeptoOS_Documentation|Top]]
----

How to open socket from CN to outside world?

----
[[KTAU]] | [[ZeptoOS_Documentation|Top]]

FAQ

2009-04-22T20:48:17Z

Hnaik:

[[KTAU]] [[ZeptoOS_Documentation|Top]]
----

How to open socket from CN to outside world?

----
[[KTAU]] [[ZeptoOS_Documentation|Top]]

(K)TAU

2009-04-22T20:48:00Z

Hnaik:

[[Zoid]] [[ZeptoOS_Documentation|Top]] [[FAQ]]
----

----
[[Zoid]] [[ZeptoOS_Documentation|Top]] [[FAQ]]

ZOID

2009-04-22T20:47:44Z

Hnaik:

[[Other Packages and Utilities]] [[ZeptoOS_Documentation|Top]] [[KTAU]]
----

Command line options

User script (here or someplace else?)

Broadcast & Performance counters

Building a new plugin

Replacement libc?

----
[[Other Packages and Utilities]] [[ZeptoOS_Documentation|Top]] [[KTAU]]

Other Packages

2009-04-22T20:47:28Z

Hnaik:

[[The ZeptoOS Ramdisk]] [[ZeptoOS_Documentation|Top]] [[Zoid]]
----

----
[[The ZeptoOS Ramdisk]] [[ZeptoOS_Documentation|Top]] [[Zoid]]

The ZeptoOS Ramdisk

2009-04-22T20:47:04Z

Hnaik:

[[The ZeptoOS V2.0 Kernel]] [[ZeptoOS_Documentation|Top]] [[Other Packages and Utilities]]
----

----
[[The ZeptoOS V2.0 Kernel]] [[ZeptoOS_Documentation|Top]] [[Other Packages and Utilities]]

The ZeptoOS V2.0 Kernel

2009-04-22T20:46:48Z

Hnaik:

[[Testing]] [[ZeptoOS_Documentation|Top]] [[The ZeptoOS Ramdisk]]
----

----
[[Testing]] [[ZeptoOS_Documentation|Top]] [[The ZeptoOS Ramdisk]]

Testing

2009-04-22T20:46:27Z

Hnaik:

[[Installation]] [[ZeptoOS_Documentation|Top]] [[The ZeptoOS V2.0 Kernel]]
----

== Using Testcode ==
Once the files installations have been done and the profiles defined by creating symbolic links to the images in the top-level directory, it is time to submit a test job. Use the test program provided with the distribution. From the top level directory:
<pre>
$ cd comm/testcodes
</pre>

=== Compiling ===

The program can be compiled on the login node using:
<pre>
$ /path/to/install/bin/zmpicc -o mpi-test-linux mpi-test.c
$ /path/to/install/bin/zmpixlc_r -openmp -o omp-test-linux omp-test.c
</pre>

=== Submitting Job ===
(For ANL Users)
The job needs to be submitted using the [[cobalt]] resource manager. For the ''mpi-test'' program use the following command:
<pre>
cqsub -n <number-of-processes> -t <time> -k <profile-name> mpi-test-linux
cqsub -n <number-of-processes> -t <time> -k <profile-name> -e OMP_NUM_THREADS=<num> omp-test-linux
</pre>

----
[[Installation]] [[ZeptoOS_Documentation|Top]] [[The ZeptoOS V2.0 Kernel]]

Installation old

2009-04-22T20:46:09Z

Hnaik:

[[The Build Process]] [[ZeptoOS_Documentation|Top]] [[Testing]]
----
In order to install the headers, libraries and the binaries, just type:
<pre>
$ python install.py /path/to/install
</pre>

This will install the following files:
<pre>
Install Home: /path/to/install
Creating install directories ...
Making /path/to/install/bin
Making /path/to/install/include
Making /path/to/install/lib

Installing mpich2 scripts ...
Installing /path/to/install/bin/zmpicc
Installing /path/to/install/bin/zmpicxx
Installing /path/to/install/bin/zmpif77
Installing /path/to/install/bin/zmpif90
Installing /path/to/install/bin/zmpixlc_r
Installing /path/to/install/bin/zmpixlc
Installing /path/to/install/bin/zmpixlcxx_r
Installing /path/to/install/bin/zmpixlcxx
Installing /path/to/install/bin/zmpixlf2003_r
Installing /path/to/install/bin/zmpixlf2003
Installing /path/to/install/bin/zmpixlf77_r
Installing /path/to/install/bin/zmpixlf77
Installing /path/to/install/bin/zmpixlf90_r
Installing /path/to/install/bin/zmpixlf90
Installing /path/to/install/bin/zmpixlf95_r
Installing /path/to/install/bin/zmpixlf95

Installing misc files ...
/path/to/install/bin/zelftool

Installing MPICH2 headers ...
/path/to/install/include/mpe_thread.h
/path/to/install/include/mpi_base.mod
/path/to/install/include/mpi_constants.mod
/path/to/install/include/mpicxx.h
/path/to/install/include/mpif.h
/path/to/install/include/mpi.h
/path/to/install/include/mpi.mod
/path/to/install/include/mpiof.h
/path/to/install/include/mpio.h
/path/to/install/include/mpi_sizeofs.mod
/path/to/install/include/mpix.h

Installing MPICH2 libraries ...
/path/to/install/lib/libcxxmpich.zcl.a
/path/to/install/lib/libfmpich_.zcl.a
/path/to/install/lib/libfmpich.zcl.a
/path/to/install/lib/libmpich.zcl.a
/path/to/install/lib/libmpich.zclf90.a

Installing SPI libraries ...
/path/to/install/lib/libSPI.zcl.a
/path/to/install/lib/libzcl.a

Installing Zoid files ...
/path/to/install/lib/libzoid_cn.a

Installing DCMF files ...
/path/to/install/include/dcmf_collectives.h
/path/to/install/include/dcmf_coremath.h
/path/to/install/include/dcmf_globalcollectives.h
/path/to/install/include/dcmf.h
/path/to/install/include/dcmf_multisend.h
/path/to/install/include/dcmf_optimath.h
/path/to/install/lib/libdcmfcoll.zcl.a
/path/to/install/lib/libdcmf.zcl.a
</pre>

== Kernel & Ramdisk ==

----
[[The Build Process]] [[ZeptoOS_Documentation|Top]] [[Testing]]

Configuration

2009-04-22T20:45:38Z

Hnaik:

[[Features]] [[ZeptoOS_Documentation|Top]] [[Installation]]
----

== Checklist ==

* It is necessary that the user is logged on the the login node.

== Configuring the Build ==

=== The Configure Script ===
Download the bzipped file on the [[Blue Gene/P]] login node. Extract the sources by using:
<pre>$ tar xjf ZeptoOS-V20-V1R3M0-beta-20090401161133.tar.bz2 </pre>

Change to the BGP top directory using:
<pre>$ cd BGP/</pre>

Then you can use the ''configure'' script to set the system tools path to default using:
<pre>$ ./configure</pre>

In order to configure the site specific paths using the tool use:
<pre>$ ./configure --edit</pre>

== Building ZeptoOS V2.0 ==

Typing ''make help'' will bring up the following menu:
<pre>
[MENU]

make - Prepare Zepto kernel and ramdisk images

make bgp-ion-ramdisk - Rebuild ION ramdisk for CNK
make bgp-ion-ramdisk-cnl - Rebuild ION ramdisk for CNL

make bgp-ion-linux - Simply use recent built or prebuilt ION kernel (no kernel rebuild)
make bgp-cn-linux - Rebuild CN ramdisk and merge with recent built or prebuilt CN kernel objs

make bgp-ion-linux-build - Rebuild ION kernel
make bgp-cn-linux-build - Rebuild CN kernel objs and CN ramdisk, then merge them into CN Kernel

make bgp-all-pkg-smart - Build packages from the prebuilt binaries
make bgp-all-pkg-rebuild - Rebuild all packages from source
</pre>

To start using the default built binaries simply type:
<pre>$ make</pre>
This will copy all the required kernel and ramdisk images to the top level directory.

=== Examining the Build Directory ===
If the build was successful, one should be able to see the following new files either rebuilt from sources or copied from their prebuilt locations:
<pre>
$ ls -l
-rwxr-xr-x 1 hnaik users 8629983 2009-01-23 17:16 BGP-CN-zImage-with-initrd.elf
-rwxr-xr-x 1 hnaik users 1444183 2009-01-23 17:03 BGP-exp-ION-zImage.elf
-rwxr-xr-x 1 hnaik users 10423112 2009-01-23 17:03 BGP-ION-ramdisk.elf
-rwxr-xr-x 1 hnaik users 10423988 2009-01-23 17:03 BGP-ION-ramdisk-for-CNL.elf
-rw-r--r-- 1 hnaik users 132 2009-01-23 17:03 bgp-ion-ramdisk-passwd.txt
-rwxr-xr-x 1 hnaik users 1351583 2009-01-23 17:08 BGP-ION-zImage.elf
</pre>

----
[[Features]] [[ZeptoOS_Documentation|Top]] [[Installation]]

Introduction

2009-04-22T20:44:38Z

Hnaik:

[[ZeptoOS_Documentation|Top]] [[Features]]
----

ZeptoOS is a research project investigating operating systems and run-time systems and libraries for petascale architectures with 10,000 to 1 million CPUs. The ZeptoOS project is a collaboration between Argonne National Laboratory and the University of Oregon.

For IBM's Bluegene/P platform, we are investigating highly efficient Linux-based compute node and I/O node kernels and advanced-functionality libraries and tools that support efficient collective operations, parallel I/O, and performance monitoring tools. Most of the time, to accomplish our Computer Science research goals we must replace IBM's closed-source components with Open Source versions that we have either written from scratch or adapted from other Open Source pieces. The new components are fast, small, reliable, infinitely flexible, and with lots of new features.

----
[[ZeptoOS_Documentation|Top]] [[Features]]

FAQ

2009-04-22T20:28:14Z

Hnaik:

[[KTAU]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top]
----

How to open socket from CN to outside world?

----
[[KTAU]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top]

Licensing

2009-04-22T20:26:37Z

Hnaik:

[https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top]
----

Short Answer: Everything is GPL and LGPL where appropriate. See the directories and individual source files for the specific license.

Rather than carry around all the license headers in each file, ZeptoOS software contains a short comment at the top of the file providing the license type and version number. For example:

# ZeptoOS_License: GPL

There is also a section that explains this, for example:

# ZEPTOOS:zepto-gpl
# Copyright: Argonne National Laboratory, Department of Energy,
# and UChicago Argonne, LLC. 2004, 2005, 2006, 2007
# ZeptoOS License: GPL
#
# This software is free. See the file ZeptoOS/misc/license.GPL
# for complete details on your rights to copy, modify, and use this
# software.
# ZEPTOOS:zepto-gpl

Those license files can be found in ZeptoOS/misc. If you are not familiar with LGPL or GPL licensing, please see the files above and also visit www.gnu.org.

Long Answer: As always, this is a tricky issue. As a general rule, we like to release software BSD, since it provides the most freedom to end users and companies. However, several companies that produce HPC products take Open Source BSD code from the community but do not voluntarily distribute their modified changes back to the community. This makes the software a dead end for computer science research, severing the relationship betweeen HPC scientists and vendors. To remedy this, we have decided to release all code under GPL or LPGL licenses, so we can partner with those vendors who actually want to collaborate on shared, Open Source code created by the HPC community.

----
[https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top]

Licensing

2009-04-22T20:26:20Z

Hnaik:

[https://wiki.mcs.anl.gov/zeptoos/index.php/Complete_ZeptoOS_Documentation Top]
----

Short Answer: Everything is GPL and LGPL where appropriate. See the directories and individual source files for the specific license.

Rather than carry around all the license headers in each file, ZeptoOS software contains a short comment at the top of the file providing the license type and version number. For example:

# ZeptoOS_License: GPL

There is also a section that explains this, for example:

# ZEPTOOS:zepto-gpl
# Copyright: Argonne National Laboratory, Department of Energy,
# and UChicago Argonne, LLC. 2004, 2005, 2006, 2007
# ZeptoOS License: GPL
#
# This software is free. See the file ZeptoOS/misc/license.GPL
# for complete details on your rights to copy, modify, and use this
# software.
# ZEPTOOS:zepto-gpl

Those license files can be found in ZeptoOS/misc. If you are not familiar with LGPL or GPL licensing, please see the files above and also visit www.gnu.org.

Long Answer: As always, this is a tricky issue. As a general rule, we like to release software BSD, since it provides the most freedom to end users and companies. However, several companies that produce HPC products take Open Source BSD code from the community but do not voluntarily distribute their modified changes back to the community. This makes the software a dead end for computer science research, severing the relationship betweeen HPC scientists and vendors. To remedy this, we have decided to release all code under GPL or LPGL licenses, so we can partner with those vendors who actually want to collaborate on shared, Open Source code created by the HPC community.

----
[https://wiki.mcs.anl.gov/zeptoos/index.php/Complete_ZeptoOS_Documentation Top]

(K)TAU

2009-04-22T20:25:43Z

Hnaik:

[[Zoid]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[FAQ]]
----

----
[[Zoid]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[FAQ]]

ZOID

2009-04-22T20:24:50Z

Hnaik:

[[Other Packages and Utilities]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[KTAU]]
----

Command line options

User script (here or someplace else?)

Broadcast & Performance counters

Building a new plugin

Replacement libc?

----
[[Other Packages and Utilities]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[KTAU]]

Other Packages

2009-04-22T20:23:23Z

Hnaik:

[[The ZeptoOS Ramdisk]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[Zoid]]
----

----
[[The ZeptoOS Ramdisk]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[Zoid]]

The ZeptoOS Ramdisk

2009-04-22T20:22:25Z

Hnaik:

[[The ZeptoOS V2.0 Kernel]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[Other Packages and Utilities]]
----

----
[[The ZeptoOS V2.0 Kernel]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[Other Packages and Utilities]]

The ZeptoOS V2.0 Kernel

2009-04-22T20:21:53Z

Hnaik:

[[Testing]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS Ramdisk]]
----

----
[[Testing]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS Ramdisk]]

Installation old

2009-04-22T20:20:58Z

Hnaik:

[[The Build Process]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[Testing]]
----
In order to install the headers, libraries and the binaries, just type:
<pre>
$ python install.py /path/to/install
</pre>

This will install the following files:
<pre>
Install Home: /path/to/install
Creating install directories ...
Making /path/to/install/bin
Making /path/to/install/include
Making /path/to/install/lib

Installing mpich2 scripts ...
Installing /path/to/install/bin/zmpicc
Installing /path/to/install/bin/zmpicxx
Installing /path/to/install/bin/zmpif77
Installing /path/to/install/bin/zmpif90
Installing /path/to/install/bin/zmpixlc_r
Installing /path/to/install/bin/zmpixlc
Installing /path/to/install/bin/zmpixlcxx_r
Installing /path/to/install/bin/zmpixlcxx
Installing /path/to/install/bin/zmpixlf2003_r
Installing /path/to/install/bin/zmpixlf2003
Installing /path/to/install/bin/zmpixlf77_r
Installing /path/to/install/bin/zmpixlf77
Installing /path/to/install/bin/zmpixlf90_r
Installing /path/to/install/bin/zmpixlf90
Installing /path/to/install/bin/zmpixlf95_r
Installing /path/to/install/bin/zmpixlf95

Installing misc files ...
/path/to/install/bin/zelftool

Installing MPICH2 headers ...
/path/to/install/include/mpe_thread.h
/path/to/install/include/mpi_base.mod
/path/to/install/include/mpi_constants.mod
/path/to/install/include/mpicxx.h
/path/to/install/include/mpif.h
/path/to/install/include/mpi.h
/path/to/install/include/mpi.mod
/path/to/install/include/mpiof.h
/path/to/install/include/mpio.h
/path/to/install/include/mpi_sizeofs.mod
/path/to/install/include/mpix.h

Installing MPICH2 libraries ...
/path/to/install/lib/libcxxmpich.zcl.a
/path/to/install/lib/libfmpich_.zcl.a
/path/to/install/lib/libfmpich.zcl.a
/path/to/install/lib/libmpich.zcl.a
/path/to/install/lib/libmpich.zclf90.a

Installing SPI libraries ...
/path/to/install/lib/libSPI.zcl.a
/path/to/install/lib/libzcl.a

Installing Zoid files ...
/path/to/install/lib/libzoid_cn.a

Installing DCMF files ...
/path/to/install/include/dcmf_collectives.h
/path/to/install/include/dcmf_coremath.h
/path/to/install/include/dcmf_globalcollectives.h
/path/to/install/include/dcmf.h
/path/to/install/include/dcmf_multisend.h
/path/to/install/include/dcmf_optimath.h
/path/to/install/lib/libdcmfcoll.zcl.a
/path/to/install/lib/libdcmf.zcl.a
</pre>

== Kernel & Ramdisk ==

----
[[The Build Process]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[Testing]]

Configuration

2009-04-21T19:44:11Z

Hnaik: /* The Configure Script */

[[Features]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[Installation]]
----

== Checklist ==

* It is necessary that the user is logged on the the login node.

== Configuring the Build ==

=== The Configure Script ===
Download the bzipped file on the [[Blue Gene/P]] login node. Extract the sources by using:
<pre>$ tar xjf ZeptoOS-V20-V1R3M0-beta-20090401161133.tar.bz2 </pre>

Change to the BGP top directory using:
<pre>$ cd BGP/</pre>

Then you can use the ''configure'' script to set the system tools path to default using:
<pre>$ ./configure</pre>

In order to configure the site specific paths using the tool use:
<pre>$ ./configure --edit</pre>

== Building ZeptoOS V2.0 ==

Typing ''make help'' will bring up the following menu:
<pre>
[MENU]

make - Prepare Zepto kernel and ramdisk images

make bgp-ion-ramdisk - Rebuild ION ramdisk for CNK
make bgp-ion-ramdisk-cnl - Rebuild ION ramdisk for CNL

make bgp-ion-linux - Simply use recent built or prebuilt ION kernel (no kernel rebuild)
make bgp-cn-linux - Rebuild CN ramdisk and merge with recent built or prebuilt CN kernel objs

make bgp-ion-linux-build - Rebuild ION kernel
make bgp-cn-linux-build - Rebuild CN kernel objs and CN ramdisk, then merge them into CN Kernel

make bgp-all-pkg-smart - Build packages from the prebuilt binaries
make bgp-all-pkg-rebuild - Rebuild all packages from source
</pre>

To start using the default built binaries simply type:
<pre>$ make</pre>
This will copy all the required kernel and ramdisk images to the top level directory.

=== Examining the Build Directory ===
If the build was successful, one should be able to see the following new files either rebuilt from sources or copied from their prebuilt locations:
<pre>
$ ls -l
-rwxr-xr-x 1 hnaik users 8629983 2009-01-23 17:16 BGP-CN-zImage-with-initrd.elf
-rwxr-xr-x 1 hnaik users 1444183 2009-01-23 17:03 BGP-exp-ION-zImage.elf
-rwxr-xr-x 1 hnaik users 10423112 2009-01-23 17:03 BGP-ION-ramdisk.elf
-rwxr-xr-x 1 hnaik users 10423988 2009-01-23 17:03 BGP-ION-ramdisk-for-CNL.elf
-rw-r--r-- 1 hnaik users 132 2009-01-23 17:03 bgp-ion-ramdisk-passwd.txt
-rwxr-xr-x 1 hnaik users 1351583 2009-01-23 17:08 BGP-ION-zImage.elf
</pre>

----
[[Features]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[Installation]]

Installation old

2009-04-21T19:19:18Z

Hnaik:

[[The Build Process]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[Testing and Troubleshooting]]
----
In order to install the headers, libraries and the binaries, just type:
<pre>
$ python install.py /path/to/install
</pre>

This will install the following files:
<pre>
Install Home: /path/to/install
Creating install directories ...
Making /path/to/install/bin
Making /path/to/install/include
Making /path/to/install/lib

Installing mpich2 scripts ...
Installing /path/to/install/bin/zmpicc
Installing /path/to/install/bin/zmpicxx
Installing /path/to/install/bin/zmpif77
Installing /path/to/install/bin/zmpif90
Installing /path/to/install/bin/zmpixlc_r
Installing /path/to/install/bin/zmpixlc
Installing /path/to/install/bin/zmpixlcxx_r
Installing /path/to/install/bin/zmpixlcxx
Installing /path/to/install/bin/zmpixlf2003_r
Installing /path/to/install/bin/zmpixlf2003
Installing /path/to/install/bin/zmpixlf77_r
Installing /path/to/install/bin/zmpixlf77
Installing /path/to/install/bin/zmpixlf90_r
Installing /path/to/install/bin/zmpixlf90
Installing /path/to/install/bin/zmpixlf95_r
Installing /path/to/install/bin/zmpixlf95

Installing misc files ...
/path/to/install/bin/zelftool

Installing MPICH2 headers ...
/path/to/install/include/mpe_thread.h
/path/to/install/include/mpi_base.mod
/path/to/install/include/mpi_constants.mod
/path/to/install/include/mpicxx.h
/path/to/install/include/mpif.h
/path/to/install/include/mpi.h
/path/to/install/include/mpi.mod
/path/to/install/include/mpiof.h
/path/to/install/include/mpio.h
/path/to/install/include/mpi_sizeofs.mod
/path/to/install/include/mpix.h

Installing MPICH2 libraries ...
/path/to/install/lib/libcxxmpich.zcl.a
/path/to/install/lib/libfmpich_.zcl.a
/path/to/install/lib/libfmpich.zcl.a
/path/to/install/lib/libmpich.zcl.a
/path/to/install/lib/libmpich.zclf90.a

Installing SPI libraries ...
/path/to/install/lib/libSPI.zcl.a
/path/to/install/lib/libzcl.a

Installing Zoid files ...
/path/to/install/lib/libzoid_cn.a

Installing DCMF files ...
/path/to/install/include/dcmf_collectives.h
/path/to/install/include/dcmf_coremath.h
/path/to/install/include/dcmf_globalcollectives.h
/path/to/install/include/dcmf.h
/path/to/install/include/dcmf_multisend.h
/path/to/install/include/dcmf_optimath.h
/path/to/install/lib/libdcmfcoll.zcl.a
/path/to/install/lib/libdcmf.zcl.a
</pre>

== Kernel & Ramdisk ==

----
[[The Build Process]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[Testing and Troubleshooting]]

Testing

2009-04-21T19:16:32Z

Hnaik: /* Submitting Job */

[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]
----

== Using Testcode ==
Once the files installations have been done and the profiles defined by creating symbolic links to the images in the top-level directory, it is time to submit a test job. Use the test program provided with the distribution. From the top level directory:
<pre>
$ cd comm/testcodes
</pre>

=== Compiling ===

The program can be compiled on the login node using:
<pre>
$ /path/to/install/bin/zmpicc -o mpi-test-linux mpi-test.c
$ /path/to/install/bin/zmpixlc_r -openmp -o omp-test-linux omp-test.c
</pre>

=== Submitting Job ===
(For ANL Users)
The job needs to be submitted using the [[cobalt]] resource manager. For the ''mpi-test'' program use the following command:
<pre>
cqsub -n <number-of-processes> -t <time> -k <profile-name> mpi-test-linux
cqsub -n <number-of-processes> -t <time> -k <profile-name> -e OMP_NUM_THREADS=<num> omp-test-linux
</pre>

----
[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]

Testing

2009-04-21T19:16:20Z

Hnaik: /* Submitting Job */

[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]
----

== Using Testcode ==
Once the files installations have been done and the profiles defined by creating symbolic links to the images in the top-level directory, it is time to submit a test job. Use the test program provided with the distribution. From the top level directory:
<pre>
$ cd comm/testcodes
</pre>

=== Compiling ===

The program can be compiled on the login node using:
<pre>
$ /path/to/install/bin/zmpicc -o mpi-test-linux mpi-test.c
$ /path/to/install/bin/zmpixlc_r -openmp -o omp-test-linux omp-test.c
</pre>

=== Submitting Job ===
(For ANL Users)
The job needs to be submitted using the [[cobalt]] resource manager. For the ''mpi-test'' program use the following command:
<pre>
cqsub -n <number-of-processes> -t <time> -k <profile-name> mpi-test-linux
cqsub -n <number-of-processes> -t <time> -k <profile-name> -e OMP_NUM_THREADS=<num> mpi-test-linux
</pre>

----
[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]

Testing

2009-04-21T19:15:17Z

Hnaik: /* Compiling */

[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]
----

== Using Testcode ==
Once the files installations have been done and the profiles defined by creating symbolic links to the images in the top-level directory, it is time to submit a test job. Use the test program provided with the distribution. From the top level directory:
<pre>
$ cd comm/testcodes
</pre>

=== Compiling ===

The program can be compiled on the login node using:
<pre>
$ /path/to/install/bin/zmpicc -o mpi-test-linux mpi-test.c
$ /path/to/install/bin/zmpixlc_r -openmp -o omp-test-linux omp-test.c
</pre>

=== Submitting Job ===
(For ANL Users)
The job needs to be submitted using the [[cobalt]] resource manager. For the ''mpi-test'' program use the following command:
<pre>cqsub -n <number-of-processes> -t <time> -k <profile-name> mpi-test-linux</pre>

----
[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]

Testing

2009-04-21T19:14:51Z

Hnaik: /* Compiling */

[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]
----

== Using Testcode ==
Once the files installations have been done and the profiles defined by creating symbolic links to the images in the top-level directory, it is time to submit a test job. Use the test program provided with the distribution. From the top level directory:
<pre>
$ cd comm/testcodes
</pre>

=== Compiling ===

The program can be compiled on the login node using:
<pre>$ /path/to/install/bin/zmpicc -o mpi-test-linux mpi-test.c</pre>
<pre>$ /path/to/install/bin/zmpixlc_r -openmp -o omp-test-linux omp-test.c</pre>

=== Submitting Job ===
(For ANL Users)
The job needs to be submitted using the [[cobalt]] resource manager. For the ''mpi-test'' program use the following command:
<pre>cqsub -n <number-of-processes> -t <time> -k <profile-name> mpi-test-linux</pre>

----
[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]

Testing

2009-04-21T19:14:00Z

Hnaik: /* Compiling */

[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]
----

== Using Testcode ==
Once the files installations have been done and the profiles defined by creating symbolic links to the images in the top-level directory, it is time to submit a test job. Use the test program provided with the distribution. From the top level directory:
<pre>
$ cd comm/testcodes
</pre>

=== Compiling ===

The program can be compiled on the login node using:
<pre>$ /path/to/install/bin/zmpicc -o mpi-test-linux mpi-test.c</pre>

=== Submitting Job ===
(For ANL Users)
The job needs to be submitted using the [[cobalt]] resource manager. For the ''mpi-test'' program use the following command:
<pre>cqsub -n <number-of-processes> -t <time> -k <profile-name> mpi-test-linux</pre>

----
[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]

Testing

2009-04-02T19:19:56Z

Hnaik: /* Submitting Job */

[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]
----

== Using Testcode ==
Once the files installations have been done and the profiles defined by creating symbolic links to the images in the top-level directory, it is time to submit a test job. Use the test program provided with the distribution. From the top level directory:
<pre>
$ cd comm/testcodes
</pre>

=== Compiling ===

The program can be compiled on the login node using:
<pre>$ /path/to/install/bin/mpicc -o mpi-test-linux mpi-test.c</pre>

=== Submitting Job ===
(For ANL Users)
The job needs to be submitted using the [[cobalt]] resource manager. For the ''mpi-test'' program use the following command:
<pre>cqsub -n <number-of-processes> -t <time> -k <profile-name> mpi-test-linux</pre>

----
[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]

Testing

2009-04-02T19:13:23Z

Hnaik: /* Submitting Job */

[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]
----

== Using Testcode ==
Once the files installations have been done and the profiles defined by creating symbolic links to the images in the top-level directory, it is time to submit a test job. Use the test program provided with the distribution. From the top level directory:
<pre>
$ cd comm/testcodes
</pre>

=== Compiling ===

The program can be compiled on the login node using:
<pre>$ /path/to/install/bin/mpicc -o mpi-test-linux mpi-test.c</pre>

=== Submitting Job ===
(For ANL Users)
The job needs to be submitted using the [[cobalt]] resource manager. For the ''hello_world'' program use the following command:
<pre>cqsub -n <number-of-processes> -t <time> -k <profile-name> mpi-test-linux</pre>

----
[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]

Testing

2009-04-02T19:12:34Z

Hnaik: /* Compiling */

[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]
----

== Using Testcode ==
Once the files installations have been done and the profiles defined by creating symbolic links to the images in the top-level directory, it is time to submit a test job. Use the test program provided with the distribution. From the top level directory:
<pre>
$ cd comm/testcodes
</pre>

=== Compiling ===

The program can be compiled on the login node using:
<pre>$ /path/to/install/bin/mpicc -o mpi-test-linux mpi-test.c</pre>

=== Submitting Job ===
(For ANL Users)
The job needs to be submitted using the [[cobalt]] resource manager. For the ''hello_world'' program use the following command:
<pre>cqsub -n <number-of-processes> -t <time> -k <profile-name> ./hello_world</pre>

----
[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]

Limitations

2009-04-02T19:06:29Z

Hnaik: New page: *With Tree Helper Thread enabled, DCMF might fail. Helper thread is disabled for now *Compute Nodes don't terminate gracefully for certain compute jobs. i.e. cnip mpi jobs have no problem

*With Tree Helper Thread enabled, DCMF might fail. Helper thread is disabled for now
*Compute Nodes don't terminate gracefully for certain compute jobs. i.e. cnip mpi jobs have no problem

Testing

2009-04-02T19:03:37Z

Hnaik: New page: Installation [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] The ZeptoOS V2.0 Kernel ---- == Using Testcode == Once the files installations have been done a...

[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]
----

== Using Testcode ==
Once the files installations have been done and the profiles defined by creating symbolic links to the images in the top-level directory, it is time to submit a test job. Use the test program provided with the distribution. From the top level directory:
<pre>
$ cd comm/testcodes
</pre>

=== Compiling ===

The program can be compiled on the login node using:
<pre>$ /path/to/install/bin/mpicc -o hello_world hello_world.c</pre>

=== Submitting Job ===
(For ANL Users)
The job needs to be submitted using the [[cobalt]] resource manager. For the ''hello_world'' program use the following command:
<pre>cqsub -n <number-of-processes> -t <time> -k <profile-name> ./hello_world</pre>

----
[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]

ZeptoOS Documentation

2009-04-02T19:03:01Z

Hnaik:

{| align="left" border="0" cellspacing="0" style="width:700px"
| [[Changes in V2.0]]
|rowspan="16"|[[Image:Zepto.png|frameless|410px]]
|-
| [[ZeptoOS V2.0 Feature List]]
|-
| [[System Requirements]]
|-
|
;Complete Documentation
# [[Introduction]]
# [[The Build Process]]
# [[Installation]]
# [[Testing]]
# [[The ZeptoOS V2.0 Kernel]]
# [[The ZeptoOS Ramdisk]]
# [[Other Packages and Utilities]]
# [[Zoid]]
# [[KTAU]]
|-
| [[Licensing]]
|-
| [[Known Bugs]]
|-
| [http://www.mcs.anl.gov/research/projects/zeptoos/cms/index.php/projects Overview of ZeptoOS Projects]
|-
|[[Source code documentation tags]]
|}

Testing and Troubleshooting

2009-04-02T18:56:48Z

Hnaik:

[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]
----

== Using Testcode ==
Once the files installations have been done and the profiles defined by creating symbolic links to the images in the top-level directory, it is time to submit a test job. Use the test program provided with the distribution. From the top level directory:
<pre>
$ cd comm/testcodes
</pre>

=== Compiling ===

The program can be compiled on the login node using:
<pre>$ /path/to/install/bin/mpicc -o hello_world hello_world.c</pre>

=== Submitting Job ===
(For ANL Users)
The job needs to be submitted using the [[cobalt]] resource manager. For the ''hello_world'' program use the following command:
<pre>cqsub -n <number-of-processes> -t <time> -k <profile-name> ./hello_world</pre>

----
[[Installation]] [https://wiki.mcs.anl.gov/zeptoos/index.php/ZeptoOS_Documentation Top] [[The ZeptoOS V2.0 Kernel]]