ck_barrier_tournament: Remove old/stale comments.

ck_pr_load is unnecessary. It is assumed a strong fence follows
initialization (through thread creation boundary, for example
or explicit IPI).
ck_pring
Samy Al Bahra 12 years ago
parent 7c56d73433
commit b4e9045c9b

@ -113,7 +113,7 @@ ck_barrier_tournament(struct ck_barrier_tournament *barrier,
int round = 1; int round = 1;
for (;; ++round) { for (;; ++round) {
switch (rounds[state->vpid][round].role) { // MIGHT NEED TO USE CK_PR_LOAD*** switch (rounds[state->vpid][round].role) {
case CK_BARRIER_TOURNAMENT_BYE: case CK_BARRIER_TOURNAMENT_BYE:
break; break;
case CK_BARRIER_TOURNAMENT_CHAMPION: case CK_BARRIER_TOURNAMENT_CHAMPION:
@ -152,7 +152,7 @@ ck_barrier_tournament(struct ck_barrier_tournament *barrier,
wakeup: wakeup:
for (round -= 1 ;; --round) { for (round -= 1 ;; --round) {
switch (rounds[state->vpid][round].role) { // MIGHT NEED TO USE CK_PR_LOAD*** switch (rounds[state->vpid][round].role) {
case CK_BARRIER_TOURNAMENT_BYE: case CK_BARRIER_TOURNAMENT_BYE:
break; break;
case CK_BARRIER_TOURNAMENT_CHAMPION: case CK_BARRIER_TOURNAMENT_CHAMPION:

Loading…
Cancel
Save