@@ -325,9 +325,17 @@ macro_rules! define_run_body {
325
325
let mut have_decayed_scorer = false ;
326
326
327
327
loop {
328
+ log_trace!( $logger, "Processing ChannelManager events..." ) ;
328
329
$process_channel_manager_events;
330
+ log_trace!( $logger, "Done processing ChannelManager events." ) ;
331
+
332
+ log_trace!( $logger, "Processing ChainMonitor events..." ) ;
329
333
$process_chain_monitor_events;
334
+ log_trace!( $logger, "Done processing ChainMonitor events." ) ;
335
+
336
+ log_trace!( $logger, "Processing OnionMessageHandler events..." ) ;
330
337
$process_onion_message_handler_events;
338
+ log_trace!( $logger, "Done processing OnionMessageHandler events." ) ;
331
339
332
340
// Note that the PeerManager::process_events may block on ChannelManager's locks,
333
341
// hence it comes last here. When the ChannelManager finishes whatever it's doing,
@@ -340,7 +348,9 @@ macro_rules! define_run_body {
340
348
// ChannelManager, we want to minimize methods blocking on a ChannelManager
341
349
// generally, and as a fallback place such blocking only immediately before
342
350
// persistence.
351
+ log_trace!( $logger, "Processing PeerManager events..." ) ;
343
352
$peer_manager. as_ref( ) . process_events( ) ;
353
+ log_trace!( $logger, "Done processing PeerManager events." ) ;
344
354
345
355
// Exit the loop if the background processor was requested to stop.
346
356
if $loop_exit_check {
0 commit comments