Reorganise some of the internals of thorn Slab:

Use LoopControl? to parallelise loops via OpenMP.

Refactor the "work horse" routines that perform the actual copy
routines. These routines are specialised for common cases that need to
execute efficiently, in particular for the cases encountered in
RotatingSymmetry?90 and RotatingSymmetry?180 when handling CCTK_REAL
variables.

Offer an additional API (Slab_MultiTransfer_Init,
Slab_MultiTransfer_Apply, Slab_MultiTransfer_Finalize) that calculates
the communication schedule only once, and then re-uses it in further
calls. This avoids some communication overhead. Remove old CVS header
comments.


git-svn-id: http://svn.cactuscode.org/arrangements/CactusNumerical/Slab/trunk@77 2e825fa2-fb71-486d-8b7f-a5ff3f0f6cb8

1 files changed, 0 insertions, 1 deletions

diff --git a/param.ccl b/param.ccl
index e3d2ae2..4dbd3c8 100644
--- a/param.ccl
+++ b/param.ccl
@@ -1,5 +1,4 @@
 # Parameter definitions for thorn Slab
-# $Header$
 
 BOOLEAN timer_output "Print slabbing timings at shutdown time" STEERABLE=always
 {