From: Matt Corallo <git@bluematt.me>
Date: Mon, 25 Oct 2021 17:31:34 +0000 (+0000)
Subject: Constify the ratio in buf limits between forward and init sync msgs
X-Git-Url: http://git.bitcoin.ninja/index.cgi?a=commitdiff_plain;h=b2b31c9752d032484bc9d84e89b8b2db7245d684;p=rust-lightning

Constify the ratio in buf limits between forward and init sync msgs
---

diff --git a/lightning/src/ln/peer_handler.rs b/lightning/src/ln/peer_handler.rs
index 74a6676d3..5150365b5 100644
--- a/lightning/src/ln/peer_handler.rs
+++ b/lightning/src/ln/peer_handler.rs
@@ -285,6 +285,10 @@ enum InitSyncTracker{
 	NodesSyncing(PublicKey),
 }
 
+/// The ratio between buffer sizes at which we stop sending initial sync messages vs when we stop
+/// forwarding messages to peers altogether.
+const FORWARD_INIT_SYNC_BUFFER_SIZE_LIMIT: usize = 2;
+
 /// When the outbound buffer has this many messages, we'll stop reading bytes from the peer until
 /// we have fewer than this many messages in the outbound buffer again.
 /// We also use this as the target number of outbound gossip messages to keep in the write buffer,
@@ -292,7 +296,7 @@ enum InitSyncTracker{
 const OUTBOUND_BUFFER_LIMIT_READ_PAUSE: usize = 10;
 /// When the outbound buffer has this many messages, we'll simply skip relaying gossip messages to
 /// the peer.
-const OUTBOUND_BUFFER_LIMIT_DROP_GOSSIP: usize = 20;
+const OUTBOUND_BUFFER_LIMIT_DROP_GOSSIP: usize = OUTBOUND_BUFFER_LIMIT_READ_PAUSE * FORWARD_INIT_SYNC_BUFFER_SIZE_LIMIT;
 
 struct Peer {
 	channel_encryptor: PeerChannelEncryptor,