Skip to content

Commit 012bc50

Browse files
authored
Merge pull request #3187 from TheBlueMatt/2024-07-routing-nits
#2803 nits
2 parents c3c909b + 7282aa7 commit 012bc50

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

lightning/src/routing/gossip.rs

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -801,9 +801,9 @@ where
801801
//
802802
// We do this by using `repr(C)`, which forces the struct to be laid out in memory the way we write
803803
// it (ensuring `last_update_message` hangs off the end and no fields are reordered after it), and
804-
// `align(32)`, ensuring the struct starts either at the start, or in the middle, of a 64b x86-64
805-
// cache line. This ensures the beginning fields (which are 31 bytes) all sit in the same cache
806-
// line.
804+
// `align(32)`, ensuring the struct starts either at the start, or in the middle, of an x86-64
805+
// 64-byte cache line. This ensures the beginning fields (which are 31 bytes) all sit in the same
806+
// cache line.
807807
#[repr(C, align(32))]
808808
#[derive(Clone, Debug, PartialEq, Eq)]
809809
/// Details about one direction of a channel as received within a [`ChannelUpdate`].
@@ -894,7 +894,7 @@ impl Readable for ChannelUpdateInfo {
894894
//
895895
// Sadly, this is not possible, however we can still do okay - all of the fields before
896896
// `one_to_two` and `two_to_one` are just under 128 bytes long, so we can ensure they sit on
897-
// adjacent cache lines (which are generally fetched together in x86_64 processors).
897+
// adjacent cache lines (which are often fetched together in x86-64 processors).
898898
//
899899
// This leaves only the two directional channel info structs on separate cache lines.
900900
//

lightning/src/routing/router.rs

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2433,10 +2433,10 @@ where L::Target: Logger {
24332433

24342434
#[allow(unused_comparisons)] // $next_hops_path_htlc_minimum_msat is 0 in some calls so rustc complains
24352435
let may_overpay_to_meet_path_minimum_msat =
2436-
((amount_to_transfer_over_msat < htlc_minimum_msat &&
2436+
(amount_to_transfer_over_msat < htlc_minimum_msat &&
24372437
recommended_value_msat >= htlc_minimum_msat) ||
2438-
(amount_to_transfer_over_msat < $next_hops_path_htlc_minimum_msat &&
2439-
recommended_value_msat >= $next_hops_path_htlc_minimum_msat));
2438+
(amount_to_transfer_over_msat < $next_hops_path_htlc_minimum_msat &&
2439+
recommended_value_msat >= $next_hops_path_htlc_minimum_msat);
24402440

24412441
let payment_failed_on_this_channel = match scid_opt {
24422442
Some(scid) => payment_params.previously_failed_channels.contains(&scid),

0 commit comments

Comments
 (0)