<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Research project Archives - Tom Barbette</title>
	<atom:link href="https://perso.uclouvain.be/tom.barbette/category/researchproject/feed/" rel="self" type="application/rss+xml" />
	<link>https://perso.uclouvain.be/tom.barbette/category/researchproject/</link>
	<description></description>
	<lastBuildDate>Sat, 31 Jan 2026 10:11:13 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2022/04/cropped-logo-uclouvain-2021-barbette-32x32.png</url>
	<title>Research project Archives - Tom Barbette</title>
	<link>https://perso.uclouvain.be/tom.barbette/category/researchproject/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>PAMO at Middleware&#8217;25</title>
		<link>https://perso.uclouvain.be/tom.barbette/pamo-at-middleware25/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Mon, 15 Dec 2025 21:10:13 +0000</pubDate>
				<category><![CDATA[Research project]]></category>
		<guid isPermaLink="false">https://perso.uclouvain.be/tom.barbette/?p=5693</guid>

					<description><![CDATA[<p>PAMO: Pattern Matching Offload for Intrusion Detection SystemsLukáš Šišmiš, Colin Evrard, Etienne Rivière, Tom Barbette This week I am going to present PAMO, a modified version of the industry-grade Suricata IDS to support offloading pattern matching to the RegEx engine of the BlueField 2. We first review and analyses the internals of IDS, focusing on &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/pamo-at-middleware25/" class="more-link">Continue reading<span class="screen-reader-text"> "PAMO at Middleware&#8217;25"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/pamo-at-middleware25/">PAMO at Middleware&#8217;25</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">PAMO: Pattern Matching Offload for Intrusion Detection Systems<br>Lukáš Šišmiš, Colin Evrard, Etienne Rivière, Tom Barbette</h2>



<p>This week I am going to present PAMO, a modified version of the industry-grade Suricata IDS to support offloading pattern matching to the RegEx engine of the BlueField 2.</p>



<p>We first review and analyses the internals of IDS, focusing on Suricata with the help of one of its maintainers, Lukas Sisimis who did a 6 month exchange with us at UCLouvain (and continued to work on it as the job was much bigger than initially envisioned).</p>



<figure class="wp-block-image size-large"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-1.png"><img fetchpriority="high" decoding="async" width="1024" height="273" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-1-1024x273.png" alt="" class="wp-image-5703" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-1-1024x273.png 1024w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-1-300x80.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-1-768x205.png 768w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-1-1536x410.png 1536w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-1.png 1612w" sizes="(max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p>We then benchmarked what the RegEx engine was capable of. </p>



<figure class="wp-block-image size-full is-resized text-center center"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-2.png"><img decoding="async" width="836" height="548" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-2.png" alt="" class="wp-image-5713" style="aspect-ratio:1.525519585667337;width:389px;height:auto" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-2.png 836w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-2-300x197.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-2-768x503.png 768w" sizes="(max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p>The answer is : 51Gbps with big packets and not too many rules (we employed the widely used Emerging Threats ruleset). Still, the RXP engine used from the ARM cores of the BlueField provides a huge help and alleviate 6 or 7 x86 cores.</p>



<figure class="wp-block-image size-large"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-3.png"><img decoding="async" width="1024" height="559" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-3-1024x559.png" alt="" class="wp-image-5723" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-3-1024x559.png 1024w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-3-300x164.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-3-768x419.png 768w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-3.png 1026w" sizes="(max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p>But the reality is that an IDS is far from being just about rules matching. And industry-grade IDS have complex processing to decide which rules should be evaluated.</p>



<p>After many challenges we evaluate PAMO using a real trace and a window-based mechanism to accelerate it using parallel traces, leaving temporal features untouched. </p>



<figure class="wp-block-image size-full"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-4.png"><img loading="lazy" decoding="async" width="828" height="372" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-4.png" alt="" class="wp-image-5733" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-4.png 828w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-4-300x135.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-4-768x345.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p>While we reduce the payload prefilter CPU processing time to peanuts, the RXP has a cost that bring the improvement to 6X. As we can&#8217;t beat Amdahl&#8217;s law, we get a 40% performance increase (this is with one core).</p>



<p>Perhaps an interesting result is how PAMO improves the performance of Suricata on the BlueField 2 itself. In that mode the IDS runs entierly on the NIC. As the ARM cores are weaker, the improvement reaches 70%.</p>



<figure class="wp-block-image size-full"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-7.png"><img loading="lazy" decoding="async" width="938" height="434" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-7.png" alt="" class="wp-image-5763" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-7.png 938w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-7-300x139.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-7-768x355.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p>Come say hello at Middleware&#8217;25 in Nashville, or check out our <a href="https://dl.acm.org/doi/10.1145/3721462.3770768">paper</a> !</p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/pamo-at-middleware25/">PAMO at Middleware&#8217;25</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>2-years post-doc position</title>
		<link>https://perso.uclouvain.be/tom.barbette/2-years-post-doc-position/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Thu, 04 Dec 2025 17:43:45 +0000</pubDate>
				<category><![CDATA[ENSG]]></category>
		<category><![CDATA[Research project]]></category>
		<guid isPermaLink="false">https://perso.uclouvain.be/tom.barbette/?p=5673</guid>

					<description><![CDATA[<p>ORGANISATION/COMPANY Université catholique de Louvain Institute of Information and Communication Technologies, Electronics and Applied Mathematics (ICTEAM) RESEARCH FIELD Networking, Systems, High-speed packet processing, SmartNICs, P4, NFV MINIMUM REQUIRED QUALIFICATIONS The candidate must have obtained a PhD in computer science before the start date. APPLICATION DEADLINE Open (continuous screening process), starting ASAP LOCATION Belgium › Louvain-la-Neuve &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/2-years-post-doc-position/" class="more-link">Continue reading<span class="screen-reader-text"> "2-years post-doc position"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/2-years-post-doc-position/">2-years post-doc position</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p><strong>ORGANISATION/COMPANY</strong></p>



<p>Université catholique de Louvain</p>



<p>Institute of Information and Communication Technologies, Electronics and Applied Mathematics (ICTEAM)</p>



<p><strong>RESEARCH FIELD</strong></p>



<p>Networking, Systems, High-speed packet processing, SmartNICs, P4, NFV</p>



<p><strong>MINIMUM REQUIRED QUALIFICATIONS</strong></p>



<p>The candidate must have obtained a PhD in computer science before the start date.</p>



<p><strong>APPLICATION DEADLINE</strong></p>



<p>Open (continuous screening process), starting ASAP</p>



<p><strong>LOCATION</strong></p>



<p>Belgium › Louvain-la-Neuve</p>



<p><strong>TYPE OF CONTRACT</strong></p>



<p>Post-Doc fellowship for 1+1 year (yearly contract)</p>



<p>2  years starting 1/1/2026</p>



<p><strong>JOB STATUS</strong></p>



<p>Full-time</p>



<p><strong>HOURS PER WEEK</strong></p>



<p>38</p>



<p><strong>OFFER DESCRIPTION</strong></p>



<p>The applicant will join the <a href="https://perso.uclouvain.be/tom.barbette/ensg/">ENSG</a> to work on leading-edge research topics in crossroad of networking and systems to build a sustainable IT infrastructure. The group is composed of the PI and 5 PhD students, and 2 post-docs.</p>



<p>The post-doc will join the PI&#8217;s group to conduct research on thematics that fit the PI&#8217;s area of expertise. The applicant will also be expected to advise master students and take a leading role with PhD students. The exact project is open to discussion, but the following project is proposed and describes well the overall direction of the lab.</p>



<p>Internet was designed at a time when computers were monolithic devices, transferring data over a network of routers and switches. This paradigm does not match the reality of today’s devices, which are composed of several elements of different nature (CPU cores, RAM, storage, NICs, GPU, etc).&nbsp; You will join the study of the fundamental challenges for the Internet to catch up with this shift of paradigm.&nbsp;<strong>Much like atoms were later refined into a set of particles, the communications of hosts must be reconsidered to enable the next leap in the Internet evolution.</strong></p>



<p>We will examine the newfound programmability of the network, i.e., P4 switches and Smart NICs, to enable sub-atomic communications over the Internet by&nbsp;<em>delegating</em>&nbsp;the intelligence out of the end “hosts”. </p>



<p>The Smart NIC of a host may essentially act as a transparent multiplexer for the sub-devices of the host, bypassing unneeded CPU transfers, and saving time and energy. The Smart NIC will be aware of power-conservative strategies when assigning requests to cores. The group is also conducting research on efficient CPU-aware software pipelines using dynamic compilation to avoid cache and branch misses. </p>



<p>Programmable switches will similarly act as coordinators of the streams through the edge. They will also lead the transfers toward the right particles among the increasingly disaggregated datacenter’s resources that are serving a provider’s content. To overcome ossification, they may expose information and negotiate a behavior for each particle’s streams to reach one possible servicing entity through the best paths. It will be possible without going back to the “ends”, and therefore enable particle-to-particle encryption as well as network efficiency.</p>



<p>The resulting low latency communication will enable future use cases such as cloud gaming and latency-critical workloads, connecting nearby particles that are getting virtually closer thanks to 5G and fiber connectivity. In the long-term, the vision enforced by the group will bring back competitiveness to the Internet by standardizing the means for such next-generation sub-atomic communication.</p>



<p><strong>SKILLS/QUALIFICATION</strong></p>



<ul class="wp-block-list">
<li>Published in known conference in the field (CoNEXT, NSDI, SIGCOMM, IMC, PAM, &#8230;) or journals (ToN, SIGCOMM CCR, TNSM, &#8230;)</li>



<li>Good comprehension of computer systems, operating systems. Knowledge of techniques like eBPF, kernel-bypass, Xilinx FPGA ecosystem, DPDK, &#8230; is a plus</li>



<li>Ease with low-level programming in C and/or Rust</li>
</ul>



<p><strong>SUBMISSION</strong></p>



<p>Please send to <a href="mailto:tom.barbette@uclouvain.be">tom.barbette@uclouvain.be</a>:</p>



<p>(a) Curriculum vitae;<br>(b) A letter of motivation;<br>(c) Links to Masters and PhD thesis (If already defended);<br>(d) List of publications and links to PDF (not behind a paywall);<br>(e) If applicable, links to examples of personal software contributions.</p>



<p><strong>REQUIRED LANGUAGES</strong></p>



<p>ENGLISH: at least B2 (upper intermediate)</p>



<p>French is not required</p>



<h2 class="wp-block-heading">Other positions</h2>



<p>See the range of possibilities at the <a href="https://perso.uclouvain.be/tom.barbette/ensg/#openpositions" data-type="page">Efficiency of Networked Systems Group</a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/2-years-post-doc-position/">2-years post-doc position</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Multi-End QUIC: A Transport Protocol to Enable One-to-Many Communications</title>
		<link>https://perso.uclouvain.be/tom.barbette/multiend/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Thu, 04 Dec 2025 09:10:51 +0000</pubDate>
				<category><![CDATA[Network]]></category>
		<category><![CDATA[Research project]]></category>
		<guid isPermaLink="false">https://perso.uclouvain.be/tom.barbette/?p=5613</guid>

					<description><![CDATA[<p>El Mehdi Makhroute, Quentin De Coninck, Tom Barbette The Internet has shifted from an end-to-end paradigm to an end-to-ends paradigm, i.e. to serve a provider&#8217;s content (e.g. a web page, an app feed, …) the client must connect to many ends to fetch various types of resources like web documents, pictures, scripts, news feed, videos, &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/multiend/" class="more-link">Continue reading<span class="screen-reader-text"> "Multi-End QUIC: A Transport Protocol to Enable One-to-Many Communications"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/multiend/">Multi-End QUIC: A Transport Protocol to Enable One-to-Many Communications</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<figure class="wp-block-embed"><div class="wp-block-embed__wrapper">
https://dl.acm.org/doi/10.1145/3769700.3771696
</div></figure>



<p><a href="https://dl.acm.org/doi/10.1145/3769700.3771696#">El Mehdi Makhroute</a>, <a href="https://dl.acm.org/doi/10.1145/3769700.3771696#">Quentin De Coninck</a>, <a href="https://dl.acm.org/doi/10.1145/3769700.3771696#">Tom Barbette</a><a href="https://dl.acm.org/doi/10.1145/3769700.3771696#tab-contributors"></a></p>



<figure class="wp-block-image size-full"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image.png"><img loading="lazy" decoding="async" width="826" height="164" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image.png" alt="" class="wp-image-5623" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image.png 826w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-300x60.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/image-768x152.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p>The Internet has shifted from an end-to-end paradigm to an end-to-ends paradigm, i.e. to serve a provider&#8217;s content (e.g. a web page, an app feed, …) the client must connect to many ends to fetch various types of resources like web documents, pictures, scripts, news feed, videos, etc… However, even the recent QUIC transport protocol failed to catch up with this change of paradigm, and the user is forced to waste many round-trip times to fetch the entire content from multiple servers. In this paper, we propose Multi-End QUIC, an extension of Multipath QUIC that enables the establishment of sub-streams directly to backend servers or third-party servers. Multi-End QUIC alleviates the need for proxies in the edge that re-encode and delay those sub-streams, that is able to bypass the relays entirely. This leads to a ~50% latency improvement in a preliminary experiment.</p>



<div data-wp-interactive="core/file" class="wp-block-file"><object data-wp-bind--hidden="!state.hasPdfPreview" hidden class="wp-block-file__embed" data="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/conext25-sw-final14.pdf" type="application/pdf" style="width:100%;height:600px" aria-label="Embed of paper."></object><a id="wp-block-file--media-2f4791c9-e0a3-496c-adb8-291aa1184a7f" href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/conext25-sw-final14.pdf">paper</a><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/12/conext25-sw-final14.pdf" class="wp-block-file__button wp-element-button" download aria-describedby="wp-block-file--media-2f4791c9-e0a3-496c-adb8-291aa1184a7f">Download</a></div>



<p><a href="https://dl.acm.org/doi/10.1145/3769700.3771696">acm</a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/multiend/">Multi-End QUIC: A Transport Protocol to Enable One-to-Many Communications</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>OpenDesc at HotNets&#8217;25 !</title>
		<link>https://perso.uclouvain.be/tom.barbette/opendesc/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Tue, 18 Nov 2025 16:14:42 +0000</pubDate>
				<category><![CDATA[Network]]></category>
		<category><![CDATA[Research project]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://perso.uclouvain.be/tom.barbette/?p=5533</guid>

					<description><![CDATA[<p>Our paper &#8220;OpenDesc: From Static NIC Descriptors to EvolvableMetadata Interfaces&#8221; will be presented today at HotNets&#8217;25. In OpenDesc, we propose to use P4 as an interface to define packet descriptors. OpenDesc enables to expose NIC capabilities and match them with application intents. We propose a prototype compiler to generate accessors that can directly extract metadata &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/opendesc/" class="more-link">Continue reading<span class="screen-reader-text"> "OpenDesc at HotNets&#8217;25 !"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/opendesc/">OpenDesc at HotNets&#8217;25 !</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>Our paper <em>&#8220;OpenDesc: From Static NIC Descriptors to Evolvable<br>Metadata Interfaces&#8221;</em> will be presented today at HotNets&#8217;25. </p>



<figure class="wp-block-image size-large"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/11/Screenshot-2025-11-18-at-17-16-03-OpenDesc-From-Static-NIC-Descriptors-to-Evolvable-Metadata-Interfaces-OpenDesc-5.pdf.png"><img loading="lazy" decoding="async" width="1024" height="423" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/11/Screenshot-2025-11-18-at-17-16-03-OpenDesc-From-Static-NIC-Descriptors-to-Evolvable-Metadata-Interfaces-OpenDesc-5.pdf-1024x423.png" alt="" class="wp-image-5573" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/11/Screenshot-2025-11-18-at-17-16-03-OpenDesc-From-Static-NIC-Descriptors-to-Evolvable-Metadata-Interfaces-OpenDesc-5.pdf-1024x423.png 1024w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/11/Screenshot-2025-11-18-at-17-16-03-OpenDesc-From-Static-NIC-Descriptors-to-Evolvable-Metadata-Interfaces-OpenDesc-5.pdf-300x124.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/11/Screenshot-2025-11-18-at-17-16-03-OpenDesc-From-Static-NIC-Descriptors-to-Evolvable-Metadata-Interfaces-OpenDesc-5.pdf-768x317.png 768w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/11/Screenshot-2025-11-18-at-17-16-03-OpenDesc-From-Static-NIC-Descriptors-to-Evolvable-Metadata-Interfaces-OpenDesc-5.pdf-1536x635.png 1536w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/11/Screenshot-2025-11-18-at-17-16-03-OpenDesc-From-Static-NIC-Descriptors-to-Evolvable-Metadata-Interfaces-OpenDesc-5.pdf.png 1612w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p>In OpenDesc, we propose to use P4 as an interface to define packet descriptors. OpenDesc enables to expose NIC capabilities and match them with application intents. We propose a prototype compiler to generate accessors that can directly extract metadata from a negotiated NIC descriptor without the need for intermediate data structures like sk_buff, xdp_sock, rte_mbuf &amp; cie.</p>



<p><em>Read more below!</em></p>



<div data-wp-interactive="core/file" class="wp-block-file"><object data-wp-bind--hidden="!state.hasPdfPreview" hidden class="wp-block-file__embed" data="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/11/OpenDesc-5.pdf" type="application/pdf" style="width:100%;height:600px" aria-label="Embed of OpenDesc."></object><a id="wp-block-file--media-e16f8335-8397-41b8-ba8f-f53385cef3b9" href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/11/OpenDesc-5.pdf">OpenDesc</a><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/11/OpenDesc-5.pdf" class="wp-block-file__button wp-element-button" download aria-describedby="wp-block-file--media-e16f8335-8397-41b8-ba8f-f53385cef3b9">Download</a></div>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/opendesc/">OpenDesc at HotNets&#8217;25 !</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Flexicast QUIC: Rethinking Multicast for the QUIC Era in SIGCOMM CCR</title>
		<link>https://perso.uclouvain.be/tom.barbette/flexicast-quic-rethinking-multicast-for-the-quic-era-in-sigcomm-ccr/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Wed, 03 Sep 2025 13:10:13 +0000</pubDate>
				<category><![CDATA[Network]]></category>
		<category><![CDATA[Research project]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://perso.uclouvain.be/tom.barbette/?p=5423</guid>

					<description><![CDATA[<p>Our latest paper with Louis Navarre, Quentin de Coninck, Tom Barbette and Olivier Bonaventure has recently appeared in SIGCOMM CCR! In short: Flexicast QUIC brings multicast back to the Internet by blending it with unicast, all within QUIC. It offers scalability where multicast works, and robustness where it doesn’t — making it a practical transport &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/flexicast-quic-rethinking-multicast-for-the-quic-era-in-sigcomm-ccr/" class="more-link">Continue reading<span class="screen-reader-text"> "Flexicast QUIC: Rethinking Multicast for the QUIC Era in SIGCOMM CCR"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/flexicast-quic-rethinking-multicast-for-the-quic-era-in-sigcomm-ccr/">Flexicast QUIC: Rethinking Multicast for the QUIC Era in SIGCOMM CCR</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>Our latest paper with Louis Navarre, Quentin de Coninck, Tom Barbette and Olivier Bonaventure has recently appeared in SIGCOMM CCR!</p>



<p><strong>In short:</strong> Flexicast QUIC brings multicast back to the Internet by blending it with unicast, all within QUIC. It offers scalability where multicast works, and robustness where it doesn’t — making it a practical transport for the next generation of large-scale applications.</p>



<div data-wp-interactive="core/file" class="wp-block-file"><object data-wp-bind--hidden="!state.hasPdfPreview" hidden class="wp-block-file__embed" data="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/Flexicast_QUIC_CCR.pdf" type="application/pdf" style="width:100%;height:600px" aria-label="Embed of Flexicast_QUIC_CCR."></object><a id="wp-block-file--media-c0257b1f-1775-4bab-9ff7-2f911f678927" href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/Flexicast_QUIC_CCR.pdf">Flexicast_QUIC_CCR</a><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/Flexicast_QUIC_CCR.pdf" class="wp-block-file__button wp-element-button" download aria-describedby="wp-block-file--media-c0257b1f-1775-4bab-9ff7-2f911f678927">Download</a></div>



<p><a href="https://dl.acm.org/doi/10.1145/3750832.3750834">acm</a> ;  <a href="https://github.com/IPNetworkingLab/flexicast-quic" target="_blank" rel="noreferrer noopener">code</a></p>



<p><strong>In long:</strong></p>



<p>When distributing live video, software updates, or cloud gaming streams, today’s Internet almost exclusively relies on <strong>unicast</strong>: each receiver gets its own copy of the data. This is simple and robust but highly inefficient, especially when thousands of receivers consume the same content. The cost is felt both at the sender — which must generate and encrypt per-receiver packets — and in the network, which carries redundant traffic.</p>



<p><strong>Multicast</strong> was designed decades ago to solve exactly this problem: a source transmits once, and routers replicate packets along a multicast tree. But despite its promise, multicast never became mainstream on the global Internet. It is difficult to deploy across ISPs, hard to monetize, and fragile — applications always need to fall back to unicast anyway. Most content providers gave up and built massive unicast infrastructures instead.</p>



<p>With the wide deployment of <strong>QUIC</strong>, a modern transport protocol running above UDP, there is a chance to revisit multicast — not at the IP layer, but directly at the transport layer. This is where <strong>Flexicast QUIC</strong> comes in.</p>



<figure class="wp-block-image size-large"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/fcquic.png"><img loading="lazy" decoding="async" width="1024" height="471" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/fcquic-1024x471.png" alt="" class="wp-image-5463" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/fcquic-1024x471.png 1024w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/fcquic-300x138.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/fcquic-768x354.png 768w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/fcquic.png 1336w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a><figcaption class="wp-element-caption">FlexiCast uses a multicast stream shared between users, and individual unicast streams to send feedback or act as a fallback. The feedback is used to send more FEC frame to compensate loss, and if the client can&#8217;t keep up, use unicast as a fallback.</figcaption></figure>



<h2 class="wp-block-heading">The Idea of Flexicast QUIC</h2>



<p>Flexicast QUIC, presented in our <em>SIGCOMM CCR 2025</em> paper, extends <strong>Multipath QUIC</strong> to combine the efficiency of multicast with the reliability of unicast. The idea is to make multicast <em>flexible</em>:</p>



<ul class="wp-block-list">
<li>Each receiver gets a <strong>unicast QUIC path</strong> for control and fallback.</li>



<li>The sender also establishes a <strong>flexicast flow</strong>: a shared, unidirectional path encrypted with a common key and intended for all receivers.</li>



<li>If multicast routing is available, this flow is carried efficiently through the network. If not, the sender can still replicate the packets itself and deliver them over unicast.</li>
</ul>



<p>Receivers can join or leave the flexicast flow at any time. If multicast fails for one receiver, it automatically falls back to unicast — without affecting others. All this happens within the same QUIC connection, so applications don’t need to juggle two protocols.</p>



<h2 class="wp-block-heading">Key Design Points</h2>



<p>Flexicast QUIC builds on QUIC’s extensible design:</p>



<ul class="wp-block-list">
<li><strong>Per-path keys</strong>: unlike regular Multipath QUIC, each unicast path and the flexicast flow use distinct encryption keys.</li>



<li><strong>Reliability</strong>: acknowledgments are sent over unicast paths, aggregated at the sender to avoid the classic <em>ack implosion</em> problem.</li>



<li><strong>Congestion control</strong>: the sender maintains per-receiver congestion states. If one receiver drags the group down, it can be removed from the flexicast flow and served over unicast.</li>
</ul>



<h2 class="wp-block-heading">Implementation and Results</h2>



<p>We implemented Flexicast QUIC in <strong>Cloudflare’s quiche</strong> library (Rust), adding ~10,000 lines of code and 5,000 lines of tests. The evaluation was run on CloudLab and emulated networks.</p>



<figure class="wp-block-image size-full"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/fc-perf.png"><img loading="lazy" decoding="async" width="971" height="965" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/fc-perf.png" alt="" class="wp-image-5483" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/fc-perf.png 971w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/fc-perf-300x298.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/fc-perf-150x150.png 150w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/fc-perf-768x763.png 768w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/09/fc-perf-100x100.png 100w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a><figcaption class="wp-element-caption">FlexiCast can scale much better than pure QUIC delivery</figcaption></figure>



<h3 class="wp-block-heading">Scalability</h3>



<ul class="wp-block-list">
<li><strong>Unicast QUIC</strong>: saturates at ~200 receivers (~20 Gbps). CPU is the bottleneck, as every packet must be encrypted per receiver.</li>



<li><strong>Flexicast QUIC</strong>: supports <strong>1000 receivers</strong> and delivers <strong>>80 Gbps</strong>, over 4× higher throughput than unicast QUIC, with acceptable CPU usage.</li>



<li>With a small acknowledgment delay (5 ms), Flexicast QUIC perfectly matches the ideal UDP baseline.</li>
</ul>



<p>Even without multicast in the network, Flexicast QUIC still helps: the sender can replicate encrypted packets using <code>sendmmsg</code>, which is far cheaper than generating per-receiver packets.</p>



<h3 class="wp-block-heading">Robustness</h3>



<p>We tested Flexicast QUIC with a 5 Mbps live video stream under failing multicast trees. Some receivers randomly lost multicast connectivity, forcing fallback to unicast. Results:</p>



<ul class="wp-block-list">
<li>Other receivers were unaffected.</li>



<li>Video quality stayed excellent (SSIM > 0.99 for 99.4% of frames).</li>



<li>Latency remained low, with only small tail increases during recovery.</li>
</ul>



<p>This shows Flexicast QUIC provides seamless continuity even when multicast is unreliable.</p>



<h2 class="wp-block-heading">Why It Matters</h2>



<p>Flexicast QUIC makes multicast practical again:</p>



<ul class="wp-block-list">
<li><strong>Efficient</strong>: one packet can serve thousands of receivers.</li>



<li><strong>Robust</strong>: unicast fallback is built-in, so failures don’t break the stream.</li>



<li><strong>Practical</strong>: works today, even without multicast routers.</li>



<li><strong>Deployable</strong>: it’s just QUIC — already used by major Internet services.</li>
</ul>



<p>This makes it promising for content delivery networks, software updates, and live streaming at scale.</p>



<h2 class="wp-block-heading">What’s Next?</h2>



<p>Our future work will explore:</p>



<ul class="wp-block-list">
<li><strong>Forward Erasure Correction</strong> to improve reliability.</li>



<li><strong>Smarter flow control</strong> for heterogeneous receivers.</li>



<li><strong>Source authentication</strong> to defend against spoofed multicast traffic.</li>



<li><strong>Multiple flexicast flows</strong> (e.g., different video bitrates).</li>



<li><strong>Dynamic key rotation</strong> for large, changing groups.</li>



<li><strong>Inter-domain deployment</strong> using AMT and TreeDN.</li>



<li><strong>New use cases</strong> like software updates or gaming.</li>
</ul>



<p>The source code and experiment scripts are open-source: <a href="https://github.com/IPNetworkingLab/flexicast-quic" rel="noreferrer noopener" target="_blank">Flexicast QUIC on GitHub</a>.</p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/flexicast-quic-rethinking-multicast-for-the-quic-era-in-sigcomm-ccr/">Flexicast QUIC: Rethinking Multicast for the QUIC Era in SIGCOMM CCR</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>ASNI: Rethinking Packet I/O for High-Performance Networking</title>
		<link>https://perso.uclouvain.be/tom.barbette/asni/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Fri, 01 Aug 2025 10:21:23 +0000</pubDate>
				<category><![CDATA[Research project]]></category>
		<guid isPermaLink="false">https://perso.uclouvain.be/tom.barbette/?p=5263</guid>

					<description><![CDATA[<p>Accepted paper to be presented at CoNEXT&#8217;25 ; Nikita Tyunyayev (UCLouvain), Clément Delzotti (UCLouvain), Haggai Eran (NVIDIA) and Tom Barbette (UCLouvain) In recent years, bypassing the Linux kernel networking stack has become a common strategy to accelerate packet processing. Techniques like DPDK eliminate kernel overhead, enabling network functions to run at much higher speeds. However, &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/asni/" class="more-link">Continue reading<span class="screen-reader-text"> "ASNI: Rethinking Packet I/O for High-Performance Networking"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/asni/">ASNI: Rethinking Packet I/O for High-Performance Networking</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p><em>Accepted paper to be presented at CoNEXT&#8217;25</em> ; <em>Nikita Tyunyayev (UCLouvain), Clément Delzotti<em> (UCLouvain)</em>, Haggai Eran (NVIDIA) and Tom Barbette (UCLouvain)</em></p>



<p>In recent years, bypassing the Linux kernel networking stack has become a common strategy to accelerate packet processing. Techniques like DPDK eliminate kernel overhead, enabling network functions to run at much higher speeds. However, these solutions do not fundamentally change how packets are exchanged between the Network Interface Controller (NIC) and the CPU.</p>



<p>At the core of this communication are descriptors: NIC-specific metadata structures that reference memory buffers and encapsulate information such as VLAN tags, flow IDs, tunnel IDs, timestamps, and L3/L4 protocol information. Because descriptor formats vary across NIC vendors, both the Linux networking stack and user-space drivers like DPDK must translate these proprietary formats into a generic representation. This translation consumes substantial CPU resources, even though most of the metadata is typically unused by applications. Additionally, applications often perform further metadata transformations themselves. <strong>X-Change</strong> addresses some of those&nbsp;inefficiencies by proposing a unified model that merges driver-level and application-level metadata.</p>



<p>Ensō introduced a streaming interface that eliminates pointer indirection by delivering packets as a continuous array. While this improves performance through better memory locality and reduced overhead, it introduces challenges when packets need to be processed out of order, requiring costly copying operations.&nbsp;</p>



<figure class="wp-block-image size-full center centered is-style-default"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/08/image-1.png"><img loading="lazy" decoding="async" width="936" height="309" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/08/image-1.png" alt="Comparing I/O processing models" class="wp-image-5293" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/08/image-1.png 936w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/08/image-1-300x99.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/08/image-1-768x254.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a><figcaption class="wp-element-caption">Comparing I/O processing models</figcaption></figure>



<p><strong>Introducing ASNI: Application-Specific Network Interface&nbsp;</strong></p>



<p>In our CoNEXT 2025 paper, we present ASNI, a new approach that builds upon, rather than replaces, the traditional packetized interface. ASNI delivers packets in large, contiguous buffers, each capable of holding multiple packets and their metadata, organized in a format tailored to the specific needs of the application. By offloading the majority of the driver datapath from the CPU to the NIC, ASNI significantly reduces CPU overhead.&nbsp;</p>



<p>Our design brings three key benefits&nbsp;</p>



<ul class="wp-block-list">
<li>&nbsp;&nbsp;&nbsp; Improved PCIe efficiency through better buffer utilization&nbsp;</li>
</ul>



<ul class="wp-block-list">
<li>&nbsp;&nbsp;&nbsp; Higher packet and metadata locality, reducing cache misses&nbsp;</li>
</ul>



<ul class="wp-block-list">
<li>&nbsp;&nbsp;&nbsp; Application-specific metadata layouts and content, avoiding unnecessary transformations&nbsp;</li>
</ul>



<figure class="wp-block-image size-full is-resized center"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/08/image.png"><img loading="lazy" decoding="async" width="624" height="367" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/08/image.png" alt="" class="wp-image-5273" style="width:489px;height:auto" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/08/image.png 624w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/08/image-300x176.png 300w" sizes="auto, (max-width: 624px) 100vw, 624px" /></a></figure>



<p>In NFV scenarios, ASNI outperforms DPDK, the dominant kernel-bypass solution, by serving 2.2× more traffic, demonstrating its effectiveness in high-throughput, low-latency environments.&nbsp;</p>



<div data-wp-interactive="core/file" class="wp-block-file"><object data-wp-bind--hidden="!state.hasPdfPreview" hidden class="wp-block-file__embed" data="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/08/asni.pdf" type="application/pdf" style="width:100%;height:600px" aria-label="Embed of ASNI Preprint."></object><a id="wp-block-file--media-aec85d11-fa87-452e-9094-98ae7c5eab37" href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/08/asni.pdf">ASNI Preprint</a><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/08/asni.pdf" class="wp-block-file__button wp-element-button" download aria-describedby="wp-block-file--media-aec85d11-fa87-452e-9094-98ae7c5eab37">Download</a></div>



<p><a href="https://dial.uclouvain.be/downloader/downloader.php?pid=boreal%3A302406&amp;datastream=PDF_01&amp;disclaimer=32d9d1e7027f43a4215a6873e6b3c15b41988ea48385a93f1dbdc30d9c8d5f6d">paper</a> ; <a href="https://github.com/UCLouvain-ENSG/ASNI">code</a> ; <a href="https://dl.acm.org/doi/10.1145/3730966">acm</a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/asni/">ASNI: Rethinking Packet I/O for High-Performance Networking</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Reframer (indirectly) presented at COP29</title>
		<link>https://perso.uclouvain.be/tom.barbette/reframer-indirectly-presented-at-cop29/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Fri, 22 Nov 2024 11:51:49 +0000</pubDate>
				<category><![CDATA[Research project]]></category>
		<guid isPermaLink="false">https://perso.uclouvain.be/tom.barbette/?p=4903</guid>

					<description><![CDATA[<p>The authors of Reframer (NSDI&#8217;22) have been noticed the technology (patented with Ericsson) has been selected among 200 technologies related to energy production or efficiency to help mitigate or adapt to climate change as part of the WIPO Green Technology Book. See https://www.wipo.int/web/green-technology-book for more information The book was presented at an official UN side &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/reframer-indirectly-presented-at-cop29/" class="more-link">Continue reading<span class="screen-reader-text"> "Reframer (indirectly) presented at COP29"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/reframer-indirectly-presented-at-cop29/">Reframer (indirectly) presented at COP29</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>The authors of <a href="https://perso.uclouvain.be/tom.barbette/?s=reframer">Reframer</a> (NSDI&#8217;22) have been noticed the technology (patented with Ericsson) has been selected among 200 technologies related to energy production or efficiency to help mitigate or adapt to climate change as part of the WIPO Green Technology Book.</p>



<figure class="wp-block-image size-full"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2024/11/image-1.png"><img loading="lazy" decoding="async" width="868" height="291" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2024/11/image-1.png" alt="Reframer" class="wp-image-4923" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2024/11/image-1.png 868w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2024/11/image-1-300x101.png 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2024/11/image-1-768x257.png 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p>See <a href="https://www.wipo.int/web/green-technology-book">https://www.wipo.int/web/green-technology-book</a> for more information</p>



<p>The book was presented at an official UN side events of the COP29.</p>



<figure class="wp-block-image size-full"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2024/11/image.png"><img loading="lazy" decoding="async" width="640" height="360" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2024/11/image.png" alt="" class="wp-image-4913" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2024/11/image.png 640w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2024/11/image-300x169.png 300w" sizes="auto, (max-width: 640px) 100vw, 640px" /></a></figure>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/reframer-indirectly-presented-at-cop29/">Reframer (indirectly) presented at COP29</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>High-Speed Forward Erasure Correction with HIRT</title>
		<link>https://perso.uclouvain.be/tom.barbette/hirt/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Thu, 31 Oct 2024 10:25:00 +0000</pubDate>
				<category><![CDATA[Research project]]></category>
		<guid isPermaLink="false">https://perso.uclouvain.be/tom.barbette/?p=5173</guid>

					<description><![CDATA[<p>Modern low-latency applications—such as online gaming, remote control systems, and real-time file access—are increasingly sensitive to packet loss and delay. Traditional transport protocols like TCP and QUIC mitigate packet loss through retransmissions, but this leads to additional round-trip delays that can significantly impact tail latency. Our paper co-authored with Louis Navarre and François Michel, &#8220;A &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/hirt/" class="more-link">Continue reading<span class="screen-reader-text"> "High-Speed Forward Erasure Correction with HIRT"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/hirt/">High-Speed Forward Erasure Correction with HIRT</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>Modern low-latency applications—such as online gaming, remote control systems, and real-time file access—are increasingly sensitive to packet loss and delay. Traditional transport protocols like TCP and QUIC mitigate packet loss through retransmissions, but this leads to additional round-trip delays that can significantly impact tail latency. Our paper co-authored with Louis Navarre and François Michel, <em>&#8220;A High-Speed Robust Tunnel using Forward Erasure Correction in Segment Routing&#8221;</em> has been published at ICNP&#8217;24 introduces <strong>HIRT</strong>, a system that applies <strong>Forward Erasure Correction (FEC)</strong> at the network layer to proactively recover from packet losses without relying on retransmissions.</p>



<figure class="wp-block-image size-large"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/07/hirt.jpg"><img loading="lazy" decoding="async" width="1024" height="226" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/07/hirt-1024x226.jpg" alt="" class="wp-image-5183" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/07/hirt-1024x226.jpg 1024w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/07/hirt-300x66.jpg 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/07/hirt-768x169.jpg 768w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/07/hirt.jpg 1487w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a><figcaption class="wp-element-caption">HIRT routers create repair packets at the transport layer, protecting a whole path at once</figcaption></figure>



<p>HIRT is built on <strong>IPv6 Segment Routing (SRv6)</strong> and leverages <strong>Random Linear Coding (RLC)</strong> to inject repair packets into the network path. These packets can be used by the receiver to reconstruct lost data without waiting for retransmissions, thereby reducing tail latency. Unlike traditional FEC schemes embedded at the transport layer, HIRT operates transparently at the network layer, requiring no changes to end-host protocols. This allows network operators to deploy it as a service that selectively protects latency-sensitive traffic across tunnels, including encrypted VPN flows.</p>



<figure class="wp-block-image size-full is-resized center"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/07/hirt-scaling.jpg"><img loading="lazy" decoding="async" width="747" height="302" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/07/hirt-scaling.jpg" alt="" class="wp-image-5193" style="width:462px;height:auto" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/07/hirt-scaling.jpg 747w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/07/hirt-scaling-300x121.jpg 300w" sizes="auto, (max-width: 706px) 89vw, (max-width: 767px) 82vw, 740px" /></a><figcaption class="wp-element-caption">HIRT implementation uses FastClick to scale on multiple cores</figcaption></figure>



<p>We implemented HIRT using <strong>FastClick</strong>, achieving line-rate processing beyond <strong>60 Gbps</strong> on commodity servers, even under <strong>>3% packet loss</strong>. The system adapts redundancy dynamically based on feedback from the receiver and employs several optimizations, including DPDK kernel bypass, SIMD acceleration, and a multithreaded architecture. Each processing stream is handled independently, avoiding bottlenecks and enabling scalability across cores. HIRT also detects overload conditions and throttles encoding/decoding to avoid contributing to packet drops under high CPU load.</p>



<figure class="wp-block-image size-full center"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/07/hirt3.jpg"><img loading="lazy" decoding="async" width="792" height="262" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/07/hirt3.jpg" alt="" class="wp-image-5203" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/07/hirt3.jpg 792w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/07/hirt3-300x99.jpg 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2025/07/hirt3-768x254.jpg 768w" sizes="auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a><figcaption class="wp-element-caption">One of HIRT evaluation uses cases shows how HIRT can recover packets lost on Starlink without waiting for retransmission</figcaption></figure>



<p>Evaluations over the <strong>Starlink LEO satellite network</strong>—which shows bursty, non-congestion-induced losses—demonstrate HIRT’s practical benefits. It reduced HTTP tail latency by up to <strong>2×</strong> and improved completion times for 1 MB file transfers by <strong>20%</strong> compared to loss-based recovery alone. Similarly, latency for NFS read/write operations improved by up to <strong>14%</strong>. Compared with prior FEC solutions like Maelstrom, HIRT achieves better recovery at lower overhead, thanks to its adaptive approach and more powerful coding strategy. Its network-layer placement also makes it easier to deploy incrementally without disrupting application stacks.</p>



<p><a href="https://dial.uclouvain.be/pr/boreal/en/object/boreal%3A292284/datastream/PDF_01/view">paper</a> ; <a href="https://github.com/louisna/HIRT">source</a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/hirt/">High-Speed Forward Erasure Correction with HIRT</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Exciting news: 2 grants accepted by FNRS</title>
		<link>https://perso.uclouvain.be/tom.barbette/exciting-news-2-grants-accepted-by-fnrs/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Thu, 14 Dec 2023 16:27:02 +0000</pubDate>
				<category><![CDATA[Research project]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://perso.uclouvain.be/tom.barbette/?p=3103</guid>

					<description><![CDATA[<p>I&#8217;m happy to share the exciting news that my project for the Incentive Grant for Scientific research (MIS) from our national fund for 470K€ (one PhD, one post-doc and equipment) was accepted, while a PhD student of our team, Clément Delzotti got his 4-year PhD funded by FNRS FRIA too! The MIS project &#8220;DHNET: The &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/exciting-news-2-grants-accepted-by-fnrs/" class="more-link">Continue reading<span class="screen-reader-text"> "Exciting news: 2 grants accepted by FNRS"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/exciting-news-2-grants-accepted-by-fnrs/">Exciting news: 2 grants accepted by FNRS</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>I&#8217;m happy to share the exciting news that my project for the Incentive Grant for Scientific research (MIS) from our national fund for 470K€ (one PhD, one post-doc and equipment) was accepted, while a PhD student of our team, Clément Delzotti got his 4-year PhD funded by FNRS FRIA too!</p>



<p>The MIS project &#8220;<em>DHNET: The Disaggregated Host Networking paradigm to enable particle-to-particle streams</em>&#8221; is a more fundamental project looking beyond the current design of the Internet, to enable more efficient communications. The Internet is built around the idea monolithic computers are communicating. Each computer gets an address, and communicate together as a whole. As physician refined the model of atoms in <em>particles</em>, the Internet needs to be redesigned to look inside computers. Components, particles, like GPU, CPU caches, TPUs, network interfaces need to communicate directly together as computers are not monolithic devices anymore, but an interconnect of many components and memory domains. Why would a transfer, say a picture generated by a cloud gaming GPU go through a CPU, a proxy, a load balancer while it could be sent through a direct path to the consumer&#8217;s screen? In practice we will use the newfound programmability of networks with programmable switches and SmartNICs to direct the data to the right <em>particle</em>. </p>



<p>The FRIA grant obtained by Clément Delzotti builds upon data acquired at the lab showing network I/O intensive application can sustain a good quality of service while achieving a 8X energy reduction by spreading differently the traffic on multiple cores and tuning frequency appropriately. The project aims at building an energy-aware data center load-balancer to reduce energy waste.</p>



<p>Therefore, expect a new PhD and post-doc position to open soon! The post-doc one is already open, just consider it can be extended <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f609.png" alt="😉" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>



<p></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/exciting-news-2-grants-accepted-by-fnrs/">Exciting news: 2 grants accepted by FNRS</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>A collection of Network Systems icons in SVG</title>
		<link>https://perso.uclouvain.be/tom.barbette/a-collection-of-network-systems-icons-in-svg/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Mon, 29 Aug 2022 13:02:21 +0000</pubDate>
				<category><![CDATA[Network]]></category>
		<category><![CDATA[Research project]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[icons]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[svg]]></category>
		<guid isPermaLink="false">https://www.tombarbette.be/?p=1233</guid>

					<description><![CDATA[<p>You can use mine as you wish, I tried to find the original authors and the appropriate license whenever I could. Don&#8217;t hesitate to send me your own.</p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/a-collection-of-network-systems-icons-in-svg/">A collection of Network Systems icons in SVG</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>You can use mine as you wish, I tried to find the original authors and the appropriate license whenever I could. Don&#8217;t hesitate to send me your own.</p>



<figure class="wp-block-image size-large is-resized"><a href="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2022/08/NVMe-redone-6.svg"><img loading="lazy" decoding="async" src="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2022/08/NVMe-redone-6.svg" alt="" class="wp-image-1285" width="130" height="215"/></a><figcaption class="wp-element-caption">NAND SSD (inspired from https://commons.wikimedia.org/wiki/File:NAND-ssd.svg, CC )</figcaption></figure>



<figure class="wp-block-image size-large is-resized"><a href="https://www.tombarbette.be/wp-content/uploads/2022/08/Ram-module-simple-3.svg"><img loading="lazy" decoding="async" src="https://www.tombarbette.be/wp-content/uploads/2022/08/Ram-module-simple-3.svg" alt="" class="wp-image-1284" width="141" height="449"/></a><figcaption class="wp-element-caption">RAM Module ( inspired from https://fr.m.wikibooks.org/wiki/Fichier:Ram-module.svg CC)</figcaption></figure>



<figure class="wp-block-image size-large is-resized"><a href="https://www.tombarbette.be/wp-content/uploads/2022/08/cpu_new-2.svg"><img loading="lazy" decoding="async" src="https://www.tombarbette.be/wp-content/uploads/2022/08/cpu_new-2.svg" alt="" class="wp-image-1261" width="247" height="248" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/cpu_new-2.svg 150w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/cpu_new-2.svg 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/cpu_new-2.svg 1024w" sizes="auto, (max-width: 247px) 100vw, 247px" /></a><figcaption class="wp-element-caption">CPU (absed on https://commons.wikimedia.org/wiki/File:Abstract_i7_CPU_icon.svg, CC)</figcaption></figure>



<figure class="wp-block-image size-large is-resized"><a href="https://www.tombarbette.be/wp-content/uploads/2022/08/dpi-1.svg"><img loading="lazy" decoding="async" src="https://www.tombarbette.be/wp-content/uploads/2022/08/dpi-1.svg" alt="" class="wp-image-1262" width="227" height="293"/></a><figcaption class="wp-element-caption">DPI (unsure but I think it&#8217;s my own. Anyway it&#8217;s standard)</figcaption></figure>



<figure class="wp-block-image size-large is-resized"><a href="https://www.tombarbette.be/wp-content/uploads/2022/08/fast-1.svg"><img loading="lazy" decoding="async" src="https://www.tombarbette.be/wp-content/uploads/2022/08/fast-1.svg" alt="" class="wp-image-1263" width="310" height="169"/></a><figcaption class="wp-element-caption">Fast (own)</figcaption></figure>



<p></p>



<figure class="wp-block-image size-large is-resized"><a href="https://www.tombarbette.be/wp-content/uploads/2022/08/gpu-3.svg"><img loading="lazy" decoding="async" src="https://www.tombarbette.be/wp-content/uploads/2022/08/gpu-3.svg" alt="" class="wp-image-1287" width="346" height="226"/></a><figcaption class="wp-element-caption">GPU (own)</figcaption></figure>



<figure class="wp-block-image size-large is-resized"><a href="https://www.tombarbette.be/wp-content/uploads/2022/08/ipsec-1.svg"><img loading="lazy" decoding="async" src="https://www.tombarbette.be/wp-content/uploads/2022/08/ipsec-1.svg" alt="" class="wp-image-1266" width="446" height="175"/></a><figcaption class="wp-element-caption">IPSEC (unsure)</figcaption></figure>



<figure class="wp-block-image size-large is-resized"><a href="https://www.tombarbette.be/wp-content/uploads/2022/08/lb-1.svg"><img loading="lazy" decoding="async" src="https://www.tombarbette.be/wp-content/uploads/2022/08/lb-1.svg" alt="" class="wp-image-1267" width="295" height="293"/></a><figcaption class="wp-element-caption">Load Balancer (unsure)</figcaption></figure>



<figure class="wp-block-image size-large is-resized"><a href="https://www.tombarbette.be/wp-content/uploads/2022/08/monitor-1.svg"><img loading="lazy" decoding="async" src="https://www.tombarbette.be/wp-content/uploads/2022/08/monitor-1.svg" alt="" class="wp-image-1268" width="316" height="299"/></a><figcaption class="wp-element-caption">Monitoring, monitor, measurements (unsure)</figcaption></figure>



<p></p>



<figure class="wp-block-image size-full"><a href="https://www.tombarbette.be/wp-content/uploads/2022/08/nic-mellanox-1.png"><img loading="lazy" decoding="async" width="375" height="298" src="https://www.tombarbette.be/wp-content/uploads/2022/08/nic-mellanox-1.png" alt="" class="wp-image-1269" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2022/08/nic-mellanox-1.png 375w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/2022/08/nic-mellanox-1-300x238.png 300w" sizes="auto, (max-width: 375px) 100vw, 375px" /></a><figcaption class="wp-element-caption">Mellanox NIC (not SVG, Mellanox)</figcaption></figure>



<figure class="wp-block-image size-large is-resized"><a href="https://www.tombarbette.be/wp-content/uploads/2022/08/nic-redone-4.svg"><img loading="lazy" decoding="async" src="https://www.tombarbette.be/wp-content/uploads/2022/08/nic-redone-4.svg" alt="" class="wp-image-1286" width="222" height="145"/></a><figcaption class="wp-element-caption">100G NIC (inspired from the above, consider my own I guess)</figcaption></figure>



<p></p>



<figure class="wp-block-image size-large is-resized"><a href="https://www.tombarbette.be/wp-content/uploads/2022/08/router-2.svg"><img loading="lazy" decoding="async" src="https://www.tombarbette.be/wp-content/uploads/2022/08/router-2.svg" alt="" class="wp-image-1274" width="148" height="148" srcset="https://perso.uclouvain.be/tom.barbette/wp-content/uploads/router-2.svg 150w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/router-2.svg 300w, https://perso.uclouvain.be/tom.barbette/wp-content/uploads/router-2.svg 1024w" sizes="auto, (max-width: 148px) 100vw, 148px" /></a><figcaption class="wp-element-caption">Router (unsure, but this is quite sandard&#8230;)</figcaption></figure>



<figure class="wp-block-image size-large is-resized"><a href="https://www.tombarbette.be/wp-content/uploads/2022/08/vlan-2.svg"><img loading="lazy" decoding="async" src="https://www.tombarbette.be/wp-content/uploads/2022/08/vlan-2.svg" alt="" class="wp-image-1276" width="631" height="248"/></a><figcaption class="wp-element-caption">VLAN (own)</figcaption></figure>



<p></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/a-collection-of-network-systems-icons-in-svg/">A collection of Network Systems icons in SVG</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
