From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [45.145.95.4]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 4F6683B2A4 for ; Tue, 2 Apr 2024 10:14:24 -0400 (EDT) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1712067263; bh=IA/deP9rjUgc19G3qnzGz8frG4fzdS9GLnE6xzOTvbw=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=n31qy7NzqBD/NQokWavfeDetD/8wg0M45XIOZ88WEFwAXpnnyw7deTJvXyAqwrcUq k+56PhYSyjnnq/uTu8E+wxPC/4sY2JqWKc2cP02ANkybxvL0ufqwbl5xX60fHTk0OU I9Y+OWBB4QqYDF/OpFUfioby+GDmhsjyOdU9uYy4UfaF9LkmBv/RsHjuKbWrYozJPr 4AiwFezjrDb6F2TOzXtMjChGM1tWj6JDzjrG0DKj19yBKjd3UaCF1LJ6dOVeVlLvTQ 13RwEOrlR1pTRgC2lnTBbEKWfk/bnk//cnSr7ALR1CRN9daQwWOJN4UkI6/XdvvAkR tOhvcrD7KGgNg== To: Juliusz Chroboczek Cc: bloat In-Reply-To: <87frw35124.wl-jch@irif.fr> References: <87frw5nrsv.wl-jch@irif.fr> <87v850n7qu.fsf@toke.dk> <87frw35124.wl-jch@irif.fr> Date: Tue, 02 Apr 2024 16:14:22 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87il0zn96p.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Bloat] The sad state of MP-TCP X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Apr 2024 14:14:24 -0000 Juliusz Chroboczek writes: >>> There should be a knob in the kernel to transparently replace TCP with >>> MP-TCP, but I couldn't find one. > >> There is, sorta. Specifically, a BPF hook that can override the protocol >> (added in kernel 6.6): >> >> https://lore.kernel.org/all/cover.1692147782.git.geliang.tang@suse.com/ > > So we're no longer doing sysctls, we're now monkey patching system > calls? I guess if it works for JavaScript, why shouldn't it work for > the kernel. If it helps you sleep at night, you can think of it more as a lisp machine than a javascript runtime ;) You're not the first to make the comparison, though: https://dl.acm.org/doi/abs/10.1145/3609021.3609306 -Toke