rx: Don't maintain maxSerial

There were no users within the code of the rx connection maxSerial
element, and maintaining it required locking on a critical path. So,
get rid of it.

Change-Id: Ied5653b6f01b78525091d8bf09bdc454002eedc0
Reviewed-on: http://gerrit.openafs.org/4797
Reviewed-by: Derrick Brashear <shadow@dementia.org>
Tested-by: Jeffrey Altman <jaltman@openafs.org>
Reviewed-by: Jeffrey Altman <jaltman@openafs.org>
This commit is contained in:
Simon Wilkinson 2010-11-05 00:23:23 +00:00 committed by Jeffrey Altman
parent fe7d38f320
commit 6a22a2f4b7
2 changed files with 0 additions and 6 deletions

View File

@ -2994,11 +2994,6 @@ rxi_ReceivePacket(struct rx_packet *np, osi_socket socket,
return np;
}
MUTEX_ENTER(&conn->conn_data_lock);
if (conn->maxSerial < np->header.serial)
conn->maxSerial = np->header.serial;
MUTEX_EXIT(&conn->conn_data_lock);
/* If the connection is in an error state, send an abort packet and ignore
* the incoming packet */
if (conn->error) {

View File

@ -246,7 +246,6 @@ struct rx_connection {
* call slot, or 0 if the slot is not busy */
afs_uint32 serial; /* Next outgoing packet serial number */
afs_uint32 lastSerial; /* # of last packet received, for computing skew */
afs_int32 maxSerial; /* largest serial number seen on incoming packets */
afs_int32 lastPacketSize; /* last >max attempt */
afs_int32 lastPacketSizeSeq; /* seq number of attempt */
afs_int32 lastPingSize; /* last MTU ping attempt */