-
-
- DEBUG1("OK, got a task (%s)", t->name);
- /* clean conditional */
- if (cond) {
- MSG_mailbox_set_cond(mailbox, NULL);
- SIMIX_cond_destroy(cond);
- }
-
- SIMIX_mutex_unlock(h->simdata->mutex);
-
- t_simdata = t->simdata;
- t_simdata->receiver = process;
- *task = t;
-
- SIMIX_mutex_lock(t_simdata->mutex);
-
- /* Transfer */
- /* create SIMIX action to the communication */
- t_simdata->comm =
- SIMIX_action_communicate(t_simdata->sender->simdata->m_host->
- simdata->smx_host,
- process->simdata->m_host->simdata->smx_host,
- t->name, t_simdata->message_size,
- t_simdata->rate);
-
- /* This is a hack. We know that both the receiver and the sender will
- need to look at the content of t_simdata->comm. And it needs to be
- destroyed. However, we don't known whether the receiver or the sender
- will get to it first. So by setting whit refcount to 2 we can enforce
- that things happen correctly. An alternative would be to only do ++ and
- -- on this refcount and to sprinkle them judiciously throughout the code,
- which appears perhaps worse? Or perhaps the refcount field of
- task->simdata can be used for this? At any rate, this will do for now */
- t_simdata->comm->refcount = 2;
-
- /* if the process is suspend, create the action but stop its execution, it will be restart when the sender process resume */
- if (MSG_process_is_suspended(t_simdata->sender)) {
- DEBUG1("Process sender (%s) suspended", t_simdata->sender->name);
- SIMIX_action_set_priority(t_simdata->comm, 0);
- }
-
- process->simdata->waiting_task = t;
- SIMIX_register_action_to_condition(t_simdata->comm, t_simdata->cond);
-
- while (1) {
- SIMIX_cond_wait(t_simdata->cond, t_simdata->mutex);
-
- if (SIMIX_action_get_state(t_simdata->comm) != SURF_ACTION_RUNNING)