Whamcloud - gitweb
LU-17665 lnet: lock primary NID only on lustre-built peer 39/54539/2
authorSerguei Smirnov <ssmirnov@whamcloud.com>
Fri, 22 Mar 2024 22:31:55 +0000 (15:31 -0700)
committerOleg Drokin <green@whamcloud.com>
Mon, 8 Apr 2024 15:37:46 +0000 (15:37 +0000)
commit90ec7361b756e685572bd168643d61bb2f4a85c4
tree809c283cf505f02d859805d20d94ca9261d5ee9c
parent94d05d0737db256a64626bfe6fa9801819230d8a
LU-17665 lnet: lock primary NID only on lustre-built peer

Primary NID locking is useful when client is connecting to a server
and peer representation of the server is provided to LNet by Lustre
via LNetAddPeer API - as interpreted from the mount command string
or llog.

When the server responds to a client, there's no need to lock
the client's primary NID.

Signed-off-by: Serguei Smirnov <ssmirnov@whamcloud.com>
Change-Id: Ifd3098b93ad2e490659eb4adbf676cba4cbdc424
Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/54539
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Frank Sehr <fsehr@whamcloud.com>
Reviewed-by: Cyril Bordage <cbordage@whamcloud.com>
Reviewed-by: Chris Horn <chris.horn@hpe.com>
Reviewed-by: Oleg Drokin <green@whamcloud.com>
lnet/lnet/peer.c