[Bloat] What is the ifb4 interface?

[Kenneth Porter <shiva@sewingwitch.com>]

[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]

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 
<https://user-images.githubusercontent.com/476401/99479609-5ad1a580-290b-11eb-8a36-e8e0757431c2.png> 
Here's the dia file (gzip'd cause github)
example.dia.gz 
<https://github.com/tohojo/sqm-scripts/files/5557551/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 
<https://github.com/tohojo/sqm-scripts/issues/125#issuecomment-729370708>, 
or unsubscribe 
<https://github.com/notifications/unsubscribe-auth/AANBO2DSP3T2M2XU42J3TFDSQM6M7ANCNFSM4TZAZ6JQ>.


[-- Attachment #2: Type: text/html, Size: 4118 bytes --]