From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-po-01v.sys.comcast.net (resqmta-po-01v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:160]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 1309A3B2A4 for ; Wed, 18 Nov 2020 08:54:33 -0500 (EST) Received: from resomta-po-17v.sys.comcast.net ([96.114.154.241]) by resqmta-po-01v.sys.comcast.net with ESMTP id fNVNkajHYjIA5fNuqkHhSK; Wed, 18 Nov 2020 13:54:32 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1605707672; bh=JaklXyCh25zybg09NbWZLGLhaIhXnU1gQohE8YQ9ag0=; h=Received:Received:Received:Subject:To:From:Message-ID:Date: MIME-Version:Content-Type; b=CcC72yOWSUGpkS/2qRuz34J8XLhlnPs+ibkuIQ6FqciNL4kXmiEPGjf7R+2ys/mF5 jXhhvE279Fap0QUEHoLP7GkKYvykdiJmmGjcmzBus6XHvwj55tsnvbbK3D3AI5BGd7 pTMWHiOMSrlBBGmVlSFeVBAZgFAh6Bdl0+IafX3uM4uV/dxpNZXZu8gn3zm9byiwHs jm7DOFj1dshhToebm5QFQxqe9Ao/kyhhFqEZZxLrt++vuVe1jN2WASGcCZthKCLre5 15wtBI3rqBCbHSX0sUAfH2Eos8fONFJqGB29X7Ii5LkxcdlRrGkxPypBoEcJm6b220 dWwQ9dOwkfo6g== Received: from home.sewingwitch.com ([98.35.153.117]) by resomta-po-17v.sys.comcast.net with ESMTPA id fNumktUUz57FwfNupkLTVh; Wed, 18 Nov 2020 13:54:32 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedujedrudefhedgheekucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedtudenucgoufhushhpvggtthfkmhhgffhomhgrihhnucdlfedtmdenucfjughrpefufhfvhffkffgfgggjtgesrgdtreertdefjeenucfhrhhomhepmfgvnhhnvghthhcurfhorhhtvghruceoshhhihhvrgesshgvfihinhhgfihithgthhdrtghomheqnecuggftrfgrthhtvghrnhephfffteduvdeggedvgeethfefleekfeejffevgeffkedvgfetvdekueduheevtefhnecuffhomhgrihhnpehgihhthhhusghushgvrhgtohhnthgvnhhtrdgtohhmpdhgihhthhhusgdrtghomhenucfkphepleekrdefhedrudehfedruddujeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopehhohhmvgdrshgvfihinhhgfihithgthhdrtghomhdpihhnvghtpeelkedrfeehrdduheefrdduudejpdhmrghilhhfrhhomhepshhhihhvrgesshgvfihinhhgfihithgthhdrtghomhdprhgtphhtthhopegslhhorghtsehlihhsthhsrdgsuhhffhgvrhgslhhorghtrdhnvght X-Xfinity-VMeta: sc=30.00;st=legit Received: from [10.96.7.39] ([10.96.7.39]) (authenticated bits=0) by home.sewingwitch.com (8.14.7/8.14.7) with ESMTP id 0AIDrHfp003939 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 18 Nov 2020 05:53:18 -0800 DKIM-Filter: OpenDKIM Filter v2.11.0 home.sewingwitch.com 0AIDrHfp003939 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sewingwitch.com; s=default; t=1605707598; bh=JaklXyCh25zybg09NbWZLGLhaIhXnU1gQohE8YQ9ag0=; h=Subject:References:To:From:Date:In-Reply-To:From; b=JtTKr3mrf1t9k4LWa2jjhYRfh3DUttNcVN5lz5FyG1KILAiO/Q3zBlFTOJpv1Z810 bSi35dDi9rmzUIDLYBBWXPjoFnq5t5pcMnYoJCeTx1XNxGLutqTa4mGuWiUNnOuKge pUooqMsRIJfGcSBvkPCwSiV48Nk1GEGSpaVRyQlo= References: To: bloat From: Kenneth Porter X-Forwarded-Message-Id: Message-ID: <97b63035-262c-f000-9107-1c9f2f2d6049@sewingwitch.com> Date: Wed, 18 Nov 2020 05:53:17 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------766B41952C2A5C5BD77C127C" Content-Language: en-GB X-Scanned-By: MIMEDefang 2.84 on 10.96.0.132 Subject: [Bloat] What is the ifb4 interface? 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: Wed, 18 Nov 2020 13:54:34 -0000 This is a multi-part message in MIME format. --------------766B41952C2A5C5BD77C127C Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit I'd never understood what the ifb4 interface was for. Here's a nice diagram from an sqm-scripts GitHub issue. Ken -------- Forwarded Message -------- Subject: Re: [tohojo/sqm-scripts] diagram needed (#125) Date: Tue, 17 Nov 2020 19:36:47 -0800 From: taggart Reply-To: tohojo/sqm-scripts To: tohojo/sqm-scripts CC: Subscribed Well it's not great, maybe something like this example Here's the dia file (gzip'd cause github) example.dia.gz I was trying to wrap my head around why ifb4 existed and how it worked. Maybe it could somehow explain that qdisc's can only work on packets leaving a device and that's the reason for the ifb4. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub , or unsubscribe . --------------766B41952C2A5C5BD77C127C Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

I'd never understood what the ifb4 interface was for. Here's a nice diagram from an sqm-scripts GitHub issue.

Ken


-------- Forwarded Message --------
Subject: Re: [tohojo/sqm-scripts] diagram needed (#125)
Date: Tue, 17 Nov 2020 19:36:47 -0800
From: taggart <notifications@github.com>
Reply-To: tohojo/sqm-scripts <reply+AANBO2FKVLZPL3BOBMDNBLV5YB345EVBNHHCY2DTJA@reply.github.com>
To: tohojo/sqm-scripts <sqm-scripts@noreply.github.com>
CC: Subscribed <subscribed@noreply.github.com>


Well it's not great, maybe something like this
example Here's the dia file (gzip'd cause github)
example.dia.gz

I was trying to wrap my head around why ifb4 existed and how it worked. Maybe it could somehow explain that qdisc's can only work on packets leaving a device and that's the reason for the ifb4.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

--------------766B41952C2A5C5BD77C127C--