From ff98db7a7345b1c59e435b19b6df9a127c011fdb Mon Sep 17 00:00:00 2001
From: eschnett <eschnett@2e825fa2-fb71-486d-8b7f-a5ff3f0f6cb8>
Date: Mon, 9 May 2011 00:15:54 +0000
Subject: 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
---
 schedule.ccl | 1 -
 1 file changed, 1 deletion(-)

(limited to 'schedule.ccl')

diff --git a/schedule.ccl b/schedule.ccl
index 74dca51..5958b4f 100644
--- a/schedule.ccl
+++ b/schedule.ccl
@@ -1,5 +1,4 @@
 # Schedule definitions for thorn Slab
-# $Header$
 
 SCHEDULE Slab_InitMPIDatatypes AT startup after Driver_Startup
 {
-- 
cgit v1.2.3