[LU-15895] o2iblnd: check if noop is needed on immediate msg rx Created: 26/May/22  Updated: 26/May/22

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

Type: Bug Priority: Minor
Reporter: Serguei Smirnov Assignee: Serguei Smirnov
Resolution: Unresolved Votes: 0
Labels: o2iblnd

Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

There are scenarios which result in short IO, which means a lot of "immediate" messages are being sent.   

If node is receiving a lot of "immediate" messages without having to send anything back, peer credits may be returned to the sender too late, causing the sender to run out of credits.

"Immediate" message in o2iblnd terms is a short, less than 4K, message which doesn't require an ack/nack to be sent back.

Currently when immediate message is received, the recipient is not checking whether hiw (high water mark) level is exceeded and it is time to return the credits (by sending a noop message). If the node is receiving only the immediate messages for a while, then only the periodic "check_connections" routine is checking whether hiw mark is exceeded, which may not be quick enough to avoid unnecessary delays.

 



 Comments   
Comment by Gerrit Updater [ 26/May/22 ]

"Serguei Smirnov <ssmirnov@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/47467
Subject: LU-15895 o2iblnd: check if noop is needed on immediate msg rx
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 61cebbcfd970d7dc513ada6ff7140d216c026a1a

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