Denis V. Lunev 8bb100c9e2 nbd: trace long NBD operations ... At the moment there are 2 sources of lengthy operations if configured: * open connection, which could retry inside and * reconnect of already opened connection These operations could be quite lengthy and cumbersome to catch thus it would be quite natural to add trace points for them. This patch is based on the original downstream work made by Vladimir. Signed-off-by: Denis V. Lunev <den@openvz.org> CC: Eric Blake <eblake@redhat.com> CC: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru> CC: Kevin Wolf <kwolf@redhat.com> CC: Hanna Reitz <hreitz@redhat.com> CC: Paolo Bonzini <pbonzini@redhat.com> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>		2022-06-29 10:57:02 +03:00
..
client-connection.c	nbd: trace long NBD operations	2022-06-29 10:57:02 +03:00
client.c	block/nbd: drop connection_co	2021-09-29 13:46:33 -05:00
common.c
meson.build	nbd: move connection code from block/nbd to nbd/client-connection	2021-06-18 10:59:53 -05:00
nbd-internal.h	configure: Add a proper check for sys/ioccom.h and use it in tpm_ioctl.h	2020-11-17 09:45:24 +01:00
server.c	nbd/server: Allow MULTI_CONN for shared writable exports	2022-05-12 13:10:52 +02:00
trace-events	nbd: trace long NBD operations	2022-06-29 10:57:02 +03:00
trace.h