Started playing around with type extensions and typebound

procedures.
Merged performance fixes from trunk.
This commit is contained in:
Salvatore Filippone
2008-09-19 16:06:44 +00:00
parent 32e6a17188
commit 00c1468c6c
285 changed files with 8931 additions and 7145 deletions
+20 -15
View File
@@ -70,21 +70,21 @@ Each point of the discretization mesh will have (at least) one
associated equation/variable, and therefore one index. We say that
point <IMG
WIDTH="10" HEIGHT="17" ALIGN="BOTTOM" BORDER="0"
SRC="img3.png"
SRC="img4.png"
ALT="$i$"> <EM>depends</EM> on point <IMG
WIDTH="11" HEIGHT="29" ALIGN="MIDDLE" BORDER="0"
SRC="img4.png"
SRC="img5.png"
ALT="$j$"> if the equation for a
variable associated with <IMG
WIDTH="10" HEIGHT="17" ALIGN="BOTTOM" BORDER="0"
SRC="img3.png"
SRC="img4.png"
ALT="$i$"> contains a term in <IMG
WIDTH="11" HEIGHT="29" ALIGN="MIDDLE" BORDER="0"
SRC="img4.png"
SRC="img5.png"
ALT="$j$">, or equivalently
if <IMG
WIDTH="53" HEIGHT="30" ALIGN="MIDDLE" BORDER="0"
SRC="img5.png"
SRC="img6.png"
ALT="$a_{ij} \ne0$">.
After the partition of the discretization mesh into <EM>sub-domains</EM>
assigned to the parallel processes,
@@ -116,7 +116,7 @@ on it. Whenever performing a computational step, such as a
matrix-vector product, the values associated with halo points are
requested from other domains. A boundary point of a given
domain is usually a halo point for some other domain<A NAME="tex2html3"
HREF="footnode.html#foot173"><SUP>2</SUP></A>; therefore
HREF="footnode.html#foot174"><SUP>2</SUP></A>; therefore
the cardinality of the boundary points set denotes the amount of data
sent to other domains.
</DD>
@@ -137,19 +137,19 @@ work&nbsp;[<A
We denote the sets of internal, boundary and halo points for a given
subdomain by <IMG
WIDTH="13" HEIGHT="14" ALIGN="BOTTOM" BORDER="0"
SRC="img6.png"
SRC="img7.png"
ALT="$\cal I$">, <IMG
WIDTH="15" HEIGHT="14" ALIGN="BOTTOM" BORDER="0"
SRC="img7.png"
SRC="img8.png"
ALT="$\cal B$"> and <IMG
WIDTH="17" HEIGHT="15" ALIGN="BOTTOM" BORDER="0"
SRC="img8.png"
SRC="img9.png"
ALT="$\cal H$">.
Each subdomain is assigned to one process; each process usually
owns one subdomain, although the user may choose to assign more than
one subdomain to a process. If each process <IMG
WIDTH="10" HEIGHT="17" ALIGN="BOTTOM" BORDER="0"
SRC="img3.png"
SRC="img4.png"
ALT="$i$"> owns one
subdomain, the number of rows in the local sparse matrix is
<!-- MATH
@@ -157,7 +157,7 @@ subdomain, the number of rows in the local sparse matrix is
-->
<IMG
WIDTH="71" HEIGHT="32" ALIGN="MIDDLE" BORDER="0"
SRC="img9.png"
SRC="img10.png"
ALT="$\vert{\cal I}_i\vert + \vert{\cal B}_i\vert$">, and the number of local columns
(i.e. those for which there exists at least one non-zero entry in the
local rows) is <!-- MATH
@@ -165,24 +165,29 @@ local rows) is <!-- MATH
-->
<IMG
WIDTH="117" HEIGHT="32" ALIGN="MIDDLE" BORDER="0"
SRC="img10.png"
SRC="img11.png"
ALT="$\vert{\cal I}_i\vert + \vert{\cal B}_i\vert +\vert{\cal H}_i\vert$">.
<P>
<DIV ALIGN="CENTER"><A NAME="fig:points"></A><A NAME="224"></A>
<DIV ALIGN="CENTER"><A NAME="fig:points"></A><A NAME="226"></A>
<TABLE>
<CAPTION ALIGN="BOTTOM"><STRONG>Figure 2:</STRONG>
Point classfication.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">
<IMG
WIDTH="318" HEIGHT="283" ALIGN="BOTTOM" BORDER="0"
SRC="img13.png"
ALT="\includegraphics[scale=0.65]{figures/points.eps}">
<!-- MATH
$\rotatebox{-90}{\includegraphics[scale=0.65]{figures/points}}$
-->
<IMG
WIDTH="132" HEIGHT="2" ALIGN="BOTTOM" BORDER="0"
SRC="img11.png"
WIDTH="131" HEIGHT="2" ALIGN="BOTTOM" BORDER="0"
SRC="img12.png"
ALT="\rotatebox{-90}{\includegraphics[scale=0.65]{figures/points}}">
</DIV></TD></TR>
</TABLE>
</DIV>