Skip to content

Commit b597908

Browse files
committed
style: rustfmt
1 parent 980a2fe commit b597908

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

quiche/src/pmtud.rs

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -89,16 +89,16 @@ impl Pmtud {
8989

9090
self.restart_pmtud();
9191

92-
// Record the failed probe again after restarting PMTUD
93-
// to ensure the next probe size is reduced (binary search down)
92+
// Record the failed probe again after restarting PMTUD to
93+
// ensure the next probe size is reduced (binary search down)
9494
// instead of resetting to the maximum MTU.
9595
//
96-
// NOTE: `failed_probe()` internally calls `update_probe_size()`,
97-
// so this is an intentional and bounded recursive call. After
98-
// `restart_pmtud()` the state is reset, and re-recording the
99-
// failed probe brings the PMTUD state back into a consistent
100-
// configuration for the next probe without causing unbounded
101-
// recursion.
96+
// NOTE: `failed_probe()` internally calls
97+
// `update_probe_size()`, so this is an intentional and
98+
// bounded recursive call. After `restart_pmtud()` the state
99+
// is reset, and re-recording the failed probe brings the
100+
// PMTUD state back into a consistent configuration for the
101+
// next probe without causing unbounded recursion.
102102
self.failed_probe(failed_probe_size);
103103

104104
return;
@@ -398,7 +398,7 @@ mod tests {
398398
// The largest successful probe should be reset after restarting PMTUD
399399
assert_eq!(pmtud.largest_successful_probe_size, None);
400400

401-
// The smallest failed probe should be recorded again after restarting PMTUD
401+
// The smallest failed probe should be recorded again
402402
assert_eq!(pmtud.smallest_failed_probe_size, Some(1300));
403403

404404
// Run the PMTUD test runner to verify handling of inconsistent results

0 commit comments

Comments
 (0)