Searched hist:"17827754 e503d6c72b05a1c4603469ec9bf35d48" (Results 1 – 2 of 2) sorted by relevance
/linux/include/trace/events/ |
H A D | dlm.h | diff 17827754e503d6c72b05a1c4603469ec9bf35d48 Thu Nov 17 23:11:45 CET 2022 Alexander Aring <aahringo@redhat.com> fs: dlm: add dst nodeid for msg tracing
In DLM when we send a dlm message it is easy to add the lock resource name, but additional lookup is required when to trace the receive message side. The idea here is to move the lookup work to the user by using a lookup to find the right send message with recv message. As note DLM can't drop any message which is guaranteed by a special session layer.
For doing the lookup a 3 tupel is required as an unique identification which is dst nodeid, src nodeid and sequence number. This patch adds the destination nodeid to the dlm message trace points. The source nodeid is given by the h_nodeid field inside the header.
Signed-off-by: Alexander Aring <aahringo@redhat.com> Signed-off-by: David Teigland <teigland@redhat.com>
|
/linux/fs/dlm/ |
H A D | midcomms.c | diff 17827754e503d6c72b05a1c4603469ec9bf35d48 Thu Nov 17 23:11:45 CET 2022 Alexander Aring <aahringo@redhat.com> fs: dlm: add dst nodeid for msg tracing
In DLM when we send a dlm message it is easy to add the lock resource name, but additional lookup is required when to trace the receive message side. The idea here is to move the lookup work to the user by using a lookup to find the right send message with recv message. As note DLM can't drop any message which is guaranteed by a special session layer.
For doing the lookup a 3 tupel is required as an unique identification which is dst nodeid, src nodeid and sequence number. This patch adds the destination nodeid to the dlm message trace points. The source nodeid is given by the h_nodeid field inside the header.
Signed-off-by: Alexander Aring <aahringo@redhat.com> Signed-off-by: David Teigland <teigland@redhat.com>
|