Edition of Thursday 12 November 2026

Performance evolution of route lookup on Linux

Comments on “Performance evolution of route lookup on Linux”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Vincent Bernat benchmarks Linux route lookup performance from kernel 2.6.32 through 7.3 on an AMD EPYC 8024P. He finds that a Linux 6.5 mitigation for the AMD SRSO vulnerability added about 200 ns to IPv6 lookups, erasing earlier gains, while IPv4 regressed mainly from a 2021 linkdown check that he…

Read the original at vincent.bernat.ch. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 23 of 106 with a score of 0.61. The panel rated it highest on new information (0.93) and technical depth (0.91), lowest on significance (0.49). Placed No. 23, No. 48 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
Detailed, measured benchmark analysis of Linux kernel route lookup regressions from speculative-execution mitigations; technically deep and well-evidenced, but niche in audience and impact.
AI judgeJudge 3gpt-5.6-luna
Detailed, reproducible Linux networking benchmarks identify mitigation and code-path regressions, quantify CPU-dependent effects, and suggest actionable mitigations. It is technically deep and well supported, though primarily relevant to networking and kernel specialists.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.61total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.49
  • Reader interest0.65
  • Audience breadth0.50
  • Practical relevance0.63
  • Substantiated0.90
  • Technical depth0.91
  • New information0.93
  • Counts against: Promotional0.03
  • Counts against: Overclaim0.13

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.510.350.620.490.27+0.24+0.119
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.520.620.820.650.30+0.26+0.170
Audience breadthHow many people who build technology does it concern?0.540.400.550.500.15+0.13+0.065
Practical relevanceHow useful is it to someone who builds software or tech products?0.630.550.720.630.17+0.22+0.139
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.950.850.910.900.10+0.05+0.045
Technical depthHow technically substantive is it?0.990.850.880.910.14+0.05+0.045
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.920.900.970.930.07+0.05+0.047
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.040.030.010.030.03−0.19−0.005
OverclaimDo the headline or conclusions claim more than the body supports?0.260.100.040.130.22−0.11−0.015
Sum of contributions+0.610
Claim-check penalty0.000
Total, as published0.610

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #23 on Rubric, 12 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-12/23/"><img src="https://rubric.hrih.si/badge/2026-11-12/23.svg" alt="Ranked #23 on Rubric, 12 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 5 no source given · 3 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. Couldn’t checkCausal conclusion

    In Linux 4.15, Wei Wang improved IPv6 lookup performance by replacing the read-write lock with an RCU and a spinlock.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “In Linux 4.15, Wei Wang im­proved the lookup per­for­mance by re­plac­ing the read-write lock with an RCU and a spin­lock in”

    The source says

    No passage could be compared.

    Source cited by the article: git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit

  2. Couldn’t checkVersion

    In Linux 5.9, Brian Vazquez removed expensive indirect calls.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “In Linux 5.9, Brian Vazquez re­moved ex­pen­sive in­di­rect calls in”

    The source says

    No passage could be compared.

    Source cited by the article: git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit

  3. No source givenNumber

    Linux 6.5 introduced a major 200 ns IPv6 route lookup regression that wiped out earlier improvements.

    The article gives no link or citation for it.

    The article says

    “The ma­jor 200 ns re­gres­sion in­tro­duced in Linux 6.5 wiped out all these im­prove­ments”

    The source says

    No source to compare with.

  4. Couldn’t checkVersion

    Linux 6.5 implements a mitigation for Speculative Return Stack Overflow, a vulnerability affecting AMD processors.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “This ver­sion im­ple­ments a mit­i­ga­tion for “Spec­u­la­tive Re­turn Stack Over­flow,” a vul­ner­a­bil­ity af­fect­ing AMD pro­ces­sors, in”

    The source says

    No passage could be compared.

    Source cited by the article: git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit

  5. No source givenNumber

    The SRSO mitigation adds about 20 cycles on each function return.

    The article gives no link or citation for it.

    The article says

    “This mit­i­ga­tion adds about 20 cy­cles on each func­tion re­turn”

    The source says

    No source to compare with.

  6. No source givenVersion

    The SRSO mitigation was backported to kernels 5.10, 5.15, 6.1, and 6.4.

    The article gives no link or citation for it.

    The article says

    “It was back­ported to older ker­nels (5.10, 5.15, 6.1, and 6.4”

    The source says

    No source to compare with.

  7. No source givenCausal conclusion

    The SRSO mitigation costs 30 ns for IPv4 lookups in Linux 6.5, less than for IPv6, because IPv4 lookups traverse about 4 function calls versus 25 for IPv6.

    The article gives no link or citation for it.

    The article says

    “The 30 ns im­pact of the mit­i­ga­tion for SRSO in Linux 6.5 is smaller than for IPv6 be­cause IPv4 route lookups tra­verse fewer func­tions”

    The source says

    No source to compare with.

  8. No source givenNumber

    Reordering the conditions in the patch improved median IPv4 lookup time from 132 to 126 cycles.

    The article gives no link or citation for it.

    The article says

    “Af­ter ap­ply­ing the patch, the me­dian im­proved from 132 to 126 cycles”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 2 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 12 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Performance evolution of route lookup on Linux”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.