root / www / software.html
Historique | Voir | Annoter | Télécharger (4,19 ko)
1 | 1 | equemene | <HTML>
|
---|---|---|---|
2 | 1 | equemene | <HEAD>
|
3 | 1 | equemene | <TITLE>HPL Software</TITLE> |
4 | 1 | equemene | </HEAD>
|
5 | 1 | equemene | |
6 | 1 | equemene | <BODY
|
7 | 1 | equemene | BGCOLOR = "WHITE" |
8 | 1 | equemene | BACKGROUND = "WHITE" |
9 | 1 | equemene | TEXT = "#000000" |
10 | 1 | equemene | VLINK = "#000099" |
11 | 1 | equemene | ALINK = "#947153" |
12 | 1 | equemene | LINK = "#0000ff"> |
13 | 1 | equemene | |
14 | 1 | equemene | <H2>HPL Software</H2> |
15 | 1 | equemene | |
16 | 1 | equemene | <H3>Download and Installation</H3> |
17 | 1 | equemene | |
18 | 1 | equemene | <OL>
|
19 | 1 | equemene | <LI>Download the <A HREF="hpl.tgz">tar-gzipped file</A>, issue then |
20 | 1 | equemene | "gunzip hpl.tgz; tar -xvf hpl.tar" and this should create an hpl |
21 | 1 | equemene | directory containing the distribution. We call this directory the |
22 | 1 | equemene | top level directory. |
23 | 1 | equemene | |
24 | 1 | equemene | <LI>Create a file Make.<arch> in the top-level directory. |
25 | 1 | equemene | For this purpose, you may want to re-use one contained in the |
26 | 1 | equemene | setup directory. This Make.<arch> file essentially contains |
27 | 1 | equemene | the compilers, libraries, and their paths to be used on your system. |
28 | 1 | equemene | |
29 | 1 | equemene | <LI>Type "make arch=<arch>". This should create an executable |
30 | 1 | equemene | in the bin/<arch> directory called xhpl. For example, on our |
31 | 1 | equemene | Linux PII cluster, I create a file called Make.Linux_PII in the |
32 | 1 | equemene | top-level directory. Then, I type "make arch=Linux_PII". This |
33 | 1 | equemene | creates the executable file bin/Linux_PII/xhpl. |
34 | 1 | equemene | |
35 | 1 | equemene | <LI>Quick check: run a few tests (assuming you have 4 nodes for
|
36 | 1 | equemene | interactive use) by issuing the following commands from the top |
37 | 1 | equemene | level directory: "cd bin/<arch> ; mpirun -np 4 xhpl". This |
38 | 1 | equemene | should produce quite a bit of meaningful output on the screen. |
39 | 1 | equemene | |
40 | 1 | equemene | <LI>Most of the performance parameters can be tuned, by modifying
|
41 | 1 | equemene | the input file bin/<arch>/HPL.dat. See the |
42 | 1 | equemene | <A HREF = "tuning.html">tuning page</A> or the TUNING file in the |
43 | 1 | equemene | top-level directory. |
44 | 1 | equemene | </OL>
|
45 | 1 | equemene | <HR NOSHADE |
46 | 1 | equemene | |
47 | 1 | equemene | <H3Compile Options</H3 |
48 | 1 | equemene | |
49 | 1 | equemene | At end the "model" Make.<arch>, the is |
50 | 1 | equemene | the to some compile of |
51 | 1 | equemene | software. list these and meaning <BR<BR |
52 | 1 | equemene | |
53 | 1 | equemene | <CENTER |
54 | 1 | equemene | <TABLE =80% BORDER |
55 | 1 | equemene | <TR<TD =LEFT<STRONG-DHPL_COPY_L</STRONG</TD |
56 | 1 | equemene | <TD =LEFTforce copy the L bcast</TD</TR |
57 | 1 | equemene | <TR<TD =LEFT<STRONG-DHPL_CALL_CBLAS</STRONG</TD |
58 | 1 | equemene | <TD =LEFTcall BLAS interface</TD</TR |
59 | 1 | equemene | <TR<TD =LEFT<STRONG-DHPL_CALL_VSIPL</STRONG</TD |
60 | 1 | equemene | <TD =LEFTcall vsip </TD</TR |
61 | 1 | equemene | <TR<TD =LEFT<STRONG-DHPL_DETAILED_TIMING</STRONG</TD |
62 | 1 | equemene | <TD =LEFTenable timers</TD</TR |
63 | 1 | equemene | </TABLE<P |
64 | 1 | equemene | </CENTER |
65 | 1 | equemene | |
66 | 1 | equemene | The must between the Fortran interface, |
67 | 1 | equemene | or BLAS interface, or VSIPL depending which |
68 | 1 | equemene | kernels available his Only of |
69 | 1 | equemene | options be If choose BLAS 77 |
70 | 1 | equemene | , it necessary fill the C |
71 | 1 | equemene | Fortran interface of Make.<arch> To |
72 | 1 | equemene | this, please to Make.<arch> contained |
73 | 1 | equemene | the directory.<BR<BR |
74 | 1 | equemene | |
75 | 1 | equemene | By HPL |
76 | 1 | equemene | <UL |
77 | 1 | equemene | <LInot L broadcast, |
78 | 1 | equemene | <LIcall BLAS 77 , |
79 | 1 | equemene | <LInot detailed information. |
80 | 1 | equemene | </UL |
81 | 1 | equemene | |
82 | 1 | equemene | As example, suppose wants software copy panel |
83 | 1 | equemene | columns a buffer broadcasting. should |
84 | 1 | equemene | more to the create appropriate |
85 | 1 | equemene | user-defined type this avoid data So, it |
86 | 1 | equemene | a idea, but insists. achieve one add |
87 | 1 | equemene | to definition HPL_OPTS the of file |
88 | 1 | equemene | <arch>. then "make arch=<arch> ; |
89 | 1 | equemene | make arch=<arch>" and executable be |
90 | 1 | equemene | with feature <BR<BR |
91 | 1 | equemene | |
92 | 1 | equemene | <HR > |
93 | 1 | equemene | <CENTER>
|
94 | 1 | equemene | <A HREF = "index.html"> [Home]</A> |
95 | 1 | equemene | <A HREF = "copyright.html"> [Copyright and Licensing Terms]</A> |
96 | 1 | equemene | <A HREF = "algorithm.html"> [Algorithm]</A> |
97 | 1 | equemene | <A HREF = "scalability.html"> [Scalability]</A> |
98 | 1 | equemene | <A HREF = "results.html"> [Performance Results]</A> |
99 | 1 | equemene | <A HREF = "documentation.html"> [Documentation]</A> |
100 | 1 | equemene | <A HREF = "software.html"> [Software]</A> |
101 | 1 | equemene | <A HREF = "faqs.html"> [FAQs]</A> |
102 | 1 | equemene | <A HREF = "tuning.html"> [Tuning]</A> |
103 | 1 | equemene | <A HREF = "errata.html"> [Errata-Bugs]</A> |
104 | 1 | equemene | <A HREF = "references.html"> [References]</A> |
105 | 1 | equemene | <A HREF = "links.html"> [Related Links]</A><BR> |
106 | 1 | equemene | </CENTER>
|
107 | 1 | equemene | <HR NOSHADE |
108 | 1 | equemene | </BODY |
109 | 1 | equemene | </HTML |