Commit 4975f92c authored by Nathalie Furmento's avatar Nathalie Furmento
Browse files

tutorials/2015-06-PATC/index.html: fixes

git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/starpu/website@15574 176f6dd6-97d6-42f4-bd05-d3db9ad07c7a
parent 3e2ef839
......@@ -57,7 +57,6 @@ module load compiler/intel
module load hardware/hwloc
module load compiler/cuda
module load mpi/intel
module load trace/fxt/0.2.13
module load runtime/starpu/1.1.4
</pre>
......@@ -70,8 +69,8 @@ Due to an issue with the NFS-mounted home, you need to redirect CUDA's cache to
<tt>
<pre>
rm -fr ~/.nv
mkdir -p /tmp/$USER-nv
ln -s /tmp/$USER-nv ~/.nv
mkdir -p /tmp/$USER/nv
ln -s /tmp/$USER/nv ~/.nv
</pre>
</tt>
</p>
......@@ -688,30 +687,21 @@ afterwards.
</p>
<p>
StarPU should be recompiled with FxT support:
To use the version of StarPU compiled with FxT support, you need to reload the
module StarPU after loading the module FxT.
</p>
<tt><pre>
$ ./configure --with-fxt --prefix=$HOME
$ make clean
$ make
$ make install
</pre></tt>
<p>
You should make sure that the summary at the end
of <tt>./configure</tt> shows that tracing was enabled:
</p>
<tt><pre>
Tracing enabled: yes
module unload runtime/starpu/1.1.4
module load trace/fxt/0.2.13
module load runtime/starpu/1.1.4
</pre></tt>
<p>
The trace file is output in <tt>/tmp</tt> by default. Since execution will
happen on a cluster node, the file will not be reachable after execution,
we need to direct StarPU to output traces to the home directory, by
using:
we need to tell StarPU to store output traces in the home directory, by
setting:
</p>
<tt><pre>
......@@ -719,7 +709,7 @@ $ export STARPU_FXT_PREFIX=$HOME/
</pre></tt>
<p>
and add it to your <tt>.bashrc</tt>.
do not forget the add the line in your file <tt>.bash_profile</tt>.
</p>
<p>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment