derek/DRAMSys
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Doc++ more info about Elwetritsch cluster usage

Browse Source
This commit is contained in:
Éder F. Zulian
2019-01-25 12:57:58 +01:00
parent 0f0963c27e
commit e979874e20
1 changed files with 29 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

44
README.md
View File

@@ -1707,17 +1707,26 @@ If you need help please contact Matthias Jung.
Users can profit of running multiple simulations automatically with
[gem5ilva](DRAMSys/library/resources/scripts/DRAMSylva/gem5ilva.sh).
### Notes for Elwetritsch users
### Notes for [Elwetritsch](https://elwe.rhrk.uni-kl.de/) Users
For using DRAMSys + gem5 on the Elwetritsch gem5 can be installed with
convenience scripts provided by
Firstly, take a look at [High Performance Computing at the TU
Kaiserslautern](https://elwe.rhrk.uni-kl.de/).
After that, please give yourself a change to learn a bit about [Batch Usage at
RHRK TU Kaiserslautern](https://elwe.rhrk.uni-kl.de/elwetritsch/batch.shtml).
This will probably save you some time later on.
When using DRAMSys + gem5 on the [Elwetritsch](https://elwe.rhrk.uni-kl.de/)
gem5 can be installed with convenience scripts provided by
[gem5.TnT](https://github.com/tukl-msd/gem5.TnT).
[gem5.TnT](https://github.com/tukl-msd/gem5.TnT) provides convenience scripts
to create disk images too. The creation of disk images for gem5 requires
superuser privilege. A solution is to copy locally created the disk images
locally to Elwetritsch (e.g., scp or mounting a folder, etc.). Since there is
no compilation copying disk images should not incur in incompatibility
[gem5.TnT](https://github.com/tukl-msd/gem5.TnT) also provides convenience scripts
to create gem5 disk images with benchmarking programs embedded. The creation
of disk images for gem5 requires superuser privilege. A solution is to copy
(e.g., using scp or mounting a folder, etc.) the locally created disk images
to Elwetritsch. Since there is no compilation involved, copying disk images
created in one machine to another machine should not incur in incompatibility
problems.
Regarding dependencies for building DRAMSys and gem5, the scripts provided in
@@ -1730,15 +1739,14 @@ On gem5.TnT repository open a gem5.TnT config file.
$ vim common/defaults.in
```
Note the variable ROOTDIR. Its default value is readonly
ROOTDIR=$HOME/gem5_tnt. That means that gem5.TnT will download to
$HOME/gem5_tnt.
Note the variable **ROOTDIR**. Its default value is *ROOTDIR=$HOME/gem5_tnt*.
That means that gem5.TnT will download to *$HOME/gem5_tnt*.
Currently on Elwetritsch the space one can use in $HOME is limited to some
tens of GiB.
Currently the space one can use in its Elwetrich *$HOME* folder is limited to
a few tens of GiB. Nevertheless, a directory **/scratch/$USER** is provided
with less space restrictions.
One can create a symlink pointing to /scratch/$USER/gem5_tnt (/scratch/$USER
is a place where lots of space are available).
One can create a symlink pointing to **/scratch/$USER/gem5_tnt**.
```bash
$ cd $SCRATCH
@@ -1791,6 +1799,12 @@ export M5_PATH=$HOME/gem5_tnt/full_system/arm/aarch-system-20180409
unset TMOUT
```
[SLURM](https://slurm.schedmd.com/overview.html) **job scripts** are available
inside the [DRAMSylva](DRAMSys/library/resources/scripts/DRAMSylva) folder.
They can be used directly without changes or as examples on how to start jobs
using nodes of the Elwetritsch cluster. Of course, one can create his/her own
job scripts.
## References