<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Transport Services: A Modern API for an Adaptive Internet Transport Layer · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2102.11035/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2102.11035/feed.xml" rel="self" type="application/rss+xml" /><item><title>Transport Services: A Modern API for an Adaptive Internet Transport Layer — mentioned by SaveTheRbtz</title><link>https://news.ycombinator.com/item?id=27202274</link><guid isPermaLink="false">urn:hackerpapers:mention:2102.11035:27202274</guid><pubDate>Tue, 18 May 2021 22:48:09 GMT</pubDate><description>&lt;p&gt;We didn&amp;#x27;t mention RSS/RPS in the post mostly because they are stable. (Albeit, relatively ineffective in terms of L2 cache misses.) FlowDirector, OTOH, breaks that stability and causes a lot of migrations, and hence a lot of re-ordering. Anyways, nice reference for TAPS! Fo those wanting to dig into it a bit more, consider reading an introductory paper (before a myriad of RFC drafts from the &amp;quot;TAPS Working Group&amp;quot;): https://arxiv.org/pdf/2102.11035.pdf PS. We went through most of our low-level web-server optimization for the Edge Network in an old blogpost…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2102.11035/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.NI</category></item></channel></rss>
