From: Sam <shorewall@net153.net>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] What is the ifb4 interface?
Date: Fri, 20 Nov 2020 15:21:29 -0600 [thread overview]
Message-ID: <5088814e-0e07-0e67-4290-a85460d4d7f9@net153.net> (raw)
In-Reply-To: <97b63035-262c-f000-9107-1c9f2f2d6049@sewingwitch.com>
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
>
prev parent reply other threads:[~2020-11-20 21:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tohojo/sqm-scripts/issues/125/729370708@github.com>
2020-11-18 13:53 ` Kenneth Porter
2020-11-20 21:21 ` Sam [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5088814e-0e07-0e67-4290-a85460d4d7f9@net153.net \
--to=shorewall@net153.net \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox