[LU-15102] Reset lnet_ni::ni_ping_count when rx is finalized, not tx Created: 14/Oct/21  Updated: 20/Nov/21  Resolved: 20/Nov/21

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

Type: Bug Priority: Minor
Reporter: Chris Horn Assignee: Chris Horn
Resolution: Fixed Votes: 0
Labels: None

Attachments: Microsoft Word LU-15102-test-results.xlsx    
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

The lnet_ni:ni_ping_count is currently reset on every (healthy) tx. We should only reset it when receiving a message over the NI. Taking net_lock 0 on every tx results in a performance loss for certain workloads.

 Comments   
Comment by Gerrit Updater [ 14/Oct/21 ]

"Chris Horn <chris.horn@hpe.com>" uploaded a new patch: https://review.whamcloud.com/45235
Subject: LU-15102 lnet: Reset ni_ping_count only on receive
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 92d5da67c9148472e08d4a22f41110572881cd6f

Comment by Chris Horn [ 15/Oct/21 ]

Attached LU-15102-test-results.xlsx showing 12.5% gain in 4k RPC/s and 11.3% gain in ping RPC/s

Comment by Gerrit Updater [ 20/Nov/21 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/45235/
Subject: LU-15102 lnet: Reset ni_ping_count only on receive
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 9cc0a5ff5fc8f45aa60cd0407ae9893d5c116ccd

Comment by Peter Jones [ 20/Nov/21 ]

Landed for 2.15

Generated at Sat Feb 10 03:15:28 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.