[LU-6594] The o2iblnd option rnr_retry_count should be removed Created: 12/May/15  Updated: 07/Oct/22  Resolved: 07/Oct/22

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Isaac Huang (Inactive) Assignee: WC Triage
Resolution: Not a Bug Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

The o2iblnd does not allow sender to overrun receive queue on the receiver - there's a credit mechanism to prevent that. So in theory the o2iblnd should never receive any RNR NAK. Therefore the rnr_retry_count option is not needed at all.

I think:

  • rnr_retry_count should be removed as a module option
  • Just in case, add some code to issue warnings should RNR NAK is ever received.

 Comments   
Comment by Isaac Huang (Inactive) [ 13/May/15 ]

RNR NAK is probably handled by OFED/HCA, i.e. not visible to the o2iblnd.

Comment by Gerrit Updater [ 10/Oct/21 ]

"Andreas Dilger <adilger@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/45176
Subject: LU-6594 o2iblnd: remove unused rnr_retry_count
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 3e2911e50f4934aeaa56859eeb4b4f5a450d624b

Generated at Sat Feb 10 02:01:33 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.