浏览代码

With the locking fixes from r8919, _starpu_request_mem_chunk_removal does not need to access the child handle any more

Samuel Thibault 12 年之前
父节点
当前提交
b1ae105330
共有 2 个文件被更改,包括 0 次插入7 次删除
  1. 0 5
      src/datawizard/filters.c
  2. 0 2
      src/datawizard/memalloc.c

+ 0 - 5
src/datawizard/filters.c

@@ -360,13 +360,8 @@ void starpu_data_unpartition(starpu_data_handle_t root_handle, unsigned gatherin
 			}
 
 			if (local->allocated && local->automatically_allocated)
-			{
 				/* free the child data copy in a lazy fashion */
-#ifdef STARPU_DEVEL
-#warning FIXME!! this needs access to the child interface, which was freed above!
-#endif
 				_starpu_request_mem_chunk_removal(child_handle, node, sizes[child]);
-			}
 		}
 
 		if (!root_handle->per_node[node].allocated)

+ 0 - 2
src/datawizard/memalloc.c

@@ -696,8 +696,6 @@ static void register_mem_chunk(struct _starpu_data_replicate *replicate, unsigne
  */
 void _starpu_request_mem_chunk_removal(starpu_data_handle_t handle, unsigned node, size_t size)
 {
-	_starpu_spin_checklocked(&handle->header_lock);
-
 	_STARPU_PTHREAD_RWLOCK_WRLOCK(&mc_rwlock[node]);
 
 	/* TODO: expensive, handle should have its own list of chunks? */