Hello All, Derrick's thread regarding abort packet containing info about throttling prompted me to resurrect this very old thread.
Jeffrey Altman <[email protected]> wrote:
>> ...
To address the question I have posed statistics would have to be collected per connection and reported in the rx_debugConn structure which currently has 9 spares. The rx_debugPeer structure currently has 10 spares.
I would like to claim two of 10 spares in the rx_debugPeer structure to report the rx throttle counts. The two new fields would be, afs_uint32 nDelayedConnAborts; afs_uint32 nDelayedCallAborts; This would allow us to help track peers which are being delayed aborts. I am still of the opinion that an over all counter would be helpful as a general metric, however at least having per peer counts would allows us to better identify the peers being shunned. With the list members' consent, I could publish Nickolai Zeldovich's rx-spec in RFC format with the rx-debug structures. Thanks, Mike _______________________________________________ AFS3-standardization mailing list [email protected] http://lists.openafs.org/mailman/listinfo/afs3-standardization
