From 9a9e5ee437932b6fa85470051d854ef3d088216d Mon Sep 17 00:00:00 2001
From: suter <frederic.suter@cc.in2p3.fr>
Date: Tue, 27 May 2014 16:45:34 +0200
Subject: [PATCH 1/1] comment a part that leads to suspect behaviors. write
 actions remain in the LMM even though the operation is over. It impacts the
 resource sharing of all subsequent actions (as if the flows were still
 active)

---
 src/surf/storage_n11.cpp | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/src/surf/storage_n11.cpp b/src/surf/storage_n11.cpp
index 832cc03314..71a03fa294 100644
--- a/src/surf/storage_n11.cpp
+++ b/src/surf/storage_n11.cpp
@@ -482,9 +482,11 @@ StorageN11Action::StorageN11Action(ModelPtr model, double cost, bool failed, Sto
   case WRITE:
     lmm_expand(model->getMaxminSystem(), storage->p_constraintWrite,
                getVariable(), 1.0);
-    ActionPtr action = this;
-    xbt_dynar_push(storage->p_writeActions, &action);
-    ref();
+
+//TODO there is something annoying with what's below. Have to sort it out...
+//    ActionPtr action = this;
+//    xbt_dynar_push(storage->p_writeActions, &action);
+//    ref();
     break;
   }
   XBT_OUT();
-- 
2.20.1