x86, UV: Correct BAU regular message type

The Broadcast Assist Unit messages have a regular or retry
message type. The regular type was not being set, but needs to
be, because the lack of a message type is sometimes used to
identify an unused entry in the message queue.
Also removing some excess comments.

Signed-off-by: Cliff Wickman <cpw@sgi.com>
Cc: gregkh@suse.de
LKML-Reference: <E1OJvNy-0004ak-Dy@eag09.americas.sgi.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>

authored by Cliff Wickman and committed by Ingo Molnar 7fba1bcd 90cc7d94

+1 -14
+1 -14
arch/x86/kernel/tlb_uv.c
··· 580 } 581 time1 = get_cycles(); 582 do { 583 - /* 584 - * Every message from any given cpu gets a unique message 585 - * sequence number. But retries use that same number. 586 - * Our message may have timed out at the destination because 587 - * all sw-ack resources are in use and there is a timeout 588 - * pending there. In that case, our last send never got 589 - * placed into the queue and we need to persist until it 590 - * does. 591 - * 592 - * Make any retry a type MSG_RETRY so that the destination will 593 - * free any resource held by a previous message from this cpu. 594 - */ 595 if (try == 0) { 596 - /* use message type set by the caller the first time */ 597 seq_number = bcp->message_number++; 598 } else { 599 - /* use RETRY type on all the rest; same sequence */ 600 bau_desc->header.msg_type = MSG_RETRY; 601 stat->s_retry_messages++; 602 }
··· 580 } 581 time1 = get_cycles(); 582 do { 583 if (try == 0) { 584 + bau_desc->header.msg_type = MSG_REGULAR; 585 seq_number = bcp->message_number++; 586 } else { 587 bau_desc->header.msg_type = MSG_RETRY; 588 stat->s_retry_messages++; 589 }