* [Bloat] What is the ifb4 interface?
[not found] <tohojo/sqm-scripts/issues/125/729370708@github.com>
@ 2020-11-18 13:53 ` Kenneth Porter
2020-11-20 21:21 ` Sam
0 siblings, 1 reply; 2+ messages in thread
From: Kenneth Porter @ 2020-11-18 13:53 UTC (permalink / raw)
To: bloat
[-- 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 --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bloat] What is the ifb4 interface?
2020-11-18 13:53 ` [Bloat] What is the ifb4 interface? Kenneth Porter
@ 2020-11-20 21:21 ` Sam
0 siblings, 0 replies; 2+ messages in thread
From: Sam @ 2020-11-20 21:21 UTC (permalink / raw)
To: bloat
While on the subject... I'm more interested in the packet flow. Like
where does iptables fit at between the ifb and eth0?
--Sam
On 11/18/20 7:53 AM, Kenneth Porter wrote:
> 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>.
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-11-20 21:21 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <tohojo/sqm-scripts/issues/125/729370708@github.com>
2020-11-18 13:53 ` [Bloat] What is the ifb4 interface? Kenneth Porter
2020-11-20 21:21 ` Sam
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox