<?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>Uncategorized Archives - Tom Barbette</title>
	<atom:link href="https://perso.uclouvain.be/tom.barbette/category/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>https://perso.uclouvain.be/tom.barbette/category/uncategorized/</link>
	<description></description>
	<lastBuildDate>Sun, 15 Nov 2026 17:25:42 +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>Uncategorized Archives - Tom Barbette</title>
	<link>https://perso.uclouvain.be/tom.barbette/category/uncategorized/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<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 class="wp-block-paragraph">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 fetchpriority="high" 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="(max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px" /></a></figure>



<p class="wp-block-paragraph">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 class="wp-block-paragraph"><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 class="wp-block-paragraph">Our latest paper with Louis Navarre, Quentin de Coninck, Tom Barbette and Olivier Bonaventure has recently appeared in SIGCOMM CCR!</p>



<p class="wp-block-paragraph"><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 class="wp-block-paragraph"><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 class="wp-block-paragraph"><strong>In long:</strong></p>



<p class="wp-block-paragraph">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 class="wp-block-paragraph"><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 class="wp-block-paragraph">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 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="(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 class="wp-block-paragraph">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 class="wp-block-paragraph">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 class="wp-block-paragraph">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 class="wp-block-paragraph">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 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="(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 class="wp-block-paragraph">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 class="wp-block-paragraph">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 class="wp-block-paragraph">This shows Flexicast QUIC provides seamless continuity even when multicast is unreliable.</p>



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



<p class="wp-block-paragraph">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 class="wp-block-paragraph">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 class="wp-block-paragraph">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 class="wp-block-paragraph">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>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 class="wp-block-paragraph">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 class="wp-block-paragraph">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 class="wp-block-paragraph">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 class="wp-block-paragraph">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 class="wp-block-paragraph"></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 class="wp-block-paragraph">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 class="wp-block-paragraph"></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 class="wp-block-paragraph"></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 class="wp-block-paragraph"></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 class="wp-block-paragraph"></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>
		<item>
		<title>Retina: Analyzing 100 GbE Traffic on Commodity Hardware</title>
		<link>https://perso.uclouvain.be/tom.barbette/retina/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Tue, 02 Aug 2022 08:03:21 +0000</pubDate>
				<category><![CDATA[Network]]></category>
		<category><![CDATA[Research project]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://www.tombarbette.be/?p=1218</guid>

					<description><![CDATA[<p>I&#8217;m pleased to announce Retina has been accepted to appear at SIGCOMM at the end of the month ! It is the result of a pleasant collaboration with Gerry Wan, Fengchen Gong and Zakir Durumeric from Stanford. Retina enables high-speed network forensics by building a binary tailored to a specific experiment written in Rust. It &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/retina/" class="more-link">Continue reading<span class="screen-reader-text"> "Retina: Analyzing 100 GbE Traffic on Commodity Hardware"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/retina/">Retina: Analyzing 100 GbE Traffic on Commodity Hardware</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">I&#8217;m pleased to announce Retina has been accepted to appear at SIGCOMM at the end of the month ! It is the result of a pleasant collaboration with Gerry Wan, Fengchen Gong and Zakir Durumeric from Stanford.</p>



<p class="wp-block-paragraph">Retina enables high-speed network forensics by building a binary tailored to a specific experiment written in Rust. It provides convenient filtering capabilities to easily answer questions such as &#8220;Is the TLS SNI really random?&#8221; or &#8220;How many TLS handshake are destined to Netflix?&#8221;. Tested at up to 160Gbps with a commodity server on a Stanford traffic TAP, it supports 5-100x higher traffic rates than standard &#8220;bloatware&#8221; IDSes.</p>



<p class="wp-block-paragraph"><a href="https://www.tombarbette.be/wp-content/uploads/2022/08/retina.pdf">paper</a> ; <a href="https://github.com/stanford-esrg/retina">github</a> ; the video will follow after SIGCOMM</p>



<p class="wp-block-paragraph"></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/retina/">Retina: Analyzing 100 GbE Traffic on Commodity Hardware</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Asynchronous Block I/O request</title>
		<link>https://perso.uclouvain.be/tom.barbette/asynchronous-block-io-request/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Tue, 28 Apr 2015 13:30:34 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://queen.run.montefiore.ulg.ac.be/~barbette/?p=494</guid>

					<description><![CDATA[<p>In the Linux kernel, Block I/O request are asynchronous. It means that when you call submit_bio(READ/WRITE, bio); or generic_make_request(&#8230;), the function will (most probably) return directly, and of course, the read is not done. So after calling bio_submit(READ&#8230;); you absolutely cannot read the content of a page added by bio_add_page(). So, how to know when &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/asynchronous-block-io-request/" class="more-link">Continue reading<span class="screen-reader-text"> "Asynchronous Block I/O request"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/asynchronous-block-io-request/">Asynchronous Block I/O request</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>In the Linux kernel, Block I/O request are asynchronous. It means that when you call submit_bio(READ/WRITE, bio); or generic_make_request(&#8230;), the function will (most probably) return directly, and of course, the read is not done. So after calling bio_submit(READ&#8230;); you absolutely cannot read the content of a page added by bio_add_page().</p>
<p>So, how to know when it is finished? You have to use bio->bi_end_io pointer function. You have to set this pointer to a function which will be called when the read has been done.</p>
<p>[code lang=&#8221;c&#8221;]void myReadIsFinished(struct bio* bio, int error) {<br />
  //Read is finished, do something with the bio content<br />
}</p>
<p>&#8230;</p>
<p>bio->bi_end_io = &#038;myReadIsFinished;<br />
bio_submit(READ, bio);[/code]</p>
<p>bio->bi_private allows you to store some pointer with the bio. Use it to know what you tried to read.</p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/asynchronous-block-io-request/">Asynchronous Block I/O request</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Limiting the incoming Block I/O requests to a device driver/md device</title>
		<link>https://perso.uclouvain.be/tom.barbette/limiting-the-incoming-block-io-requests-to-a-device-drivermd-device/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Fri, 17 Apr 2015 11:52:08 +0000</pubDate>
				<category><![CDATA[INFO-0940 Operating Systems – 2014-2015 Specific posts]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://queen.run.montefiore.ulg.ac.be/~barbette/?p=468</guid>

					<description><![CDATA[<p>When implementing a device driver or a MD device which can receive Block I/O (struct bio in the kernel), you can receive BIO of nearly any size, with any number of segments (segments are discontinued parts of a common buffer, defined in a bio request). You may want to limit : &#8211; The number of segments &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/limiting-the-incoming-block-io-requests-to-a-device-drivermd-device/" class="more-link">Continue reading<span class="screen-reader-text"> "Limiting the incoming Block I/O requests to a device driver/md device"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/limiting-the-incoming-block-io-requests-to-a-device-drivermd-device/">Limiting the incoming Block I/O requests to a device driver/md device</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>When implementing a device driver or a MD device which can receive Block I/O (<em>struct bio</em> in the kernel), you can receive BIO of nearly any size, with any number of segments (segments are discontinued parts of a common buffer, defined in a bio request). You may want to limit :</p>
<p>&#8211; The number of segments you can receive with<br />
[code lang=&#8221;c&#8221;]blk_queue_max_segments(queue, <em>X</em>);[/code]<br />
Where X is the number of segments per <em>struct bio</em></p>
<p>&#8211; The maximal size of the request :<br />
[code lang=&#8221;c&#8221;]blk_queue_max_hw_sectors(queue, <em>Y</em>);[/code]<br />
Where Y is the maximal size in sectors</p>
<p>For a md device, the queue can be recovered with mddev-&gt;queue</p>
<p>The combination of the two allows to limit ensure that all bio request have always maximum X segments for a maximal size of Y sectors.</p>
<p>It is used in raid0 with Y=mddev-&gt;chunk_sectors to ensure that no request is bigger than one chunk, so any request cross at most one chunk boundary. And with X=1, it allows to use the bio_split function to split a request which would span on the two sides of a chunk boundary.</p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/limiting-the-incoming-block-io-requests-to-a-device-drivermd-device/">Limiting the incoming Block I/O requests to a device driver/md device</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Automatically find all returned e-mails from &#8220;Undelivered messages&#8221;</title>
		<link>https://perso.uclouvain.be/tom.barbette/automatically-find-all-returned-e-mails-from-undelivered-messages/</link>
		
		<dc:creator><![CDATA[Tom Barbette]]></dc:creator>
		<pubDate>Mon, 17 Mar 2014 08:58:48 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Unix]]></category>
		<guid isPermaLink="false">http://queen.run.montefiore.ulg.ac.be/~barbette/?p=245</guid>

					<description><![CDATA[<p>If you&#8217;ve got your mails under a text format in a folder (like the unix Maildir) you can use this command to extract the e-mails with a 550 return error. &#160; cat * &#124; grep --text -Pzoi '([a-z0-9._-]+@[a-z0-9.]+)(?=.*host.*said.*55[0-9])' &#160; The first command in the pipe, cat, send all files content to the next command in &#8230; </p>
<p class="link-more"><a href="https://perso.uclouvain.be/tom.barbette/automatically-find-all-returned-e-mails-from-undelivered-messages/" class="more-link">Continue reading<span class="screen-reader-text"> "Automatically find all returned e-mails from &#8220;Undelivered messages&#8221;"</span></a></p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/automatically-find-all-returned-e-mails-from-undelivered-messages/">Automatically find all returned e-mails from &#8220;Undelivered messages&#8221;</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>If you&#8217;ve got your mails under a text format in a folder (like the unix Maildir) you can use this command to extract the e-mails with a 550 return error.</p>
<p>&nbsp;</p>
<p><code>cat * | grep --text -Pzoi '([a-z0-9._-]+@[a-z0-9.]+)(?=.*host.*said.*55[0-9])'</code></p>
<p>&nbsp;</p>
<p>The first command in the pipe, cat, send all files content to the next command in the pipe : grep. Grep is removing everything except what is an adress, and only if it is followed by &#8220;host * said * 55[0-9] &#8221; where * can be everything and [0-9] is a number between 0 and 9. We also use the &#8211;text parameter because some mails could contain binary data.</p>
<p>&nbsp;</p>
<p>As grep give you the mail separated by new line, and an sql command takes a list of strings separated by comma, you can copy the list in gedit or notepad++ and use search-&gt;replace to change them in the format &#8216;mail1&#8217;, &#8216;mail2&#8217;, &#8230; You have to put &#8220;(.*)&#8221; in the search field, &#8220;&#8216;\1&#8217;,&#8221; in the replace by field, and select &#8220;regular expression&#8221;. You then place the result in the parenthesis after IN, in SQL command below :</p>
<p>&nbsp;</p>
<p><code lang="sql">UPDATE contact SET mail='' WHERE mail IN ('bad@hotmail.com', 'error@mail.com')</code></p>
<p>&nbsp;</p>
<p>The post <a href="https://perso.uclouvain.be/tom.barbette/automatically-find-all-returned-e-mails-from-undelivered-messages/">Automatically find all returned e-mails from &#8220;Undelivered messages&#8221;</a> appeared first on <a href="https://perso.uclouvain.be/tom.barbette">Tom Barbette</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
