From: Mario Ferreira <liouxbsd@gmail.com>
To: Benjamin Cronce <bcronce@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] "BBR" TCP patches submitted to linux kernel
Date: Fri, 30 Sep 2016 01:58:39 +0000 [thread overview]
Message-ID: <CAH44DxbK5n94PkBLORHfduS_cuop+nGBUeTqrPHyMzUwnpzohQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ_ENFG2NAu+Q_7S6wrObGBTtqjrhuMcqm_m7X=+SsY7OUc_mw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
On Thu, Sep 29, 2016, 20:26 Benjamin Cronce <bcronce@gmail.com> wrote:
> On Thu, Sep 29, 2016 at 6:24 AM, Mário Sérgio Fujikawa Ferreira <
> liouxbsd@gmail.com> wrote:
>
>> [...]
> FreeBSD support would be excellent but I don't even have reviewed the
>> license to be sure if we need a clean room development (hence I haven't
>> read the code) or we can try to relocate it directly. On a side FreeBSD
>> note, I'm hopeful for
>>
>> 1. Packet pacing (https://wiki.freebsd.org/DevSummit/201606/Transport)
>> 2. ipfw/dummynet AQM with FQ-Codel (
>> https://lists.freebsd.org/pipermail/freebsd-ipfw/2016-February/006026.html
>> )
>>
>> It's a great foot in the door, but PFSense does not use dummynet for
> interface shaping, they
>
use PF. We need someone to get fq-codel into PF.
>
For pfsense you would need someone to code it into ALTQ if I read it right.
A possible approach then would be contacting the original ALTQ developers
https://www.sonycsl.co.jp/person/kjc/kjc/software.html
--
Mario S F Ferreira - Brazil - "I guess this is a signature."
feature, n: a documented bug | bug, n: an undocumented feature
[-- Attachment #2: Type: text/html, Size: 3186 bytes --]
next prev parent reply other threads:[~2016-09-30 1:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 21:04 Dave Taht
2016-09-16 21:11 ` Steinar H. Gunderson
2016-09-16 21:14 ` Eric Dumazet
2016-09-16 22:29 ` Dave Taht
2016-09-29 11:24 ` Mário Sérgio Fujikawa Ferreira
2016-09-29 19:43 ` Dave Täht
2016-09-29 20:35 ` Aaron Wood
2016-09-30 8:12 ` Mikael Abrahamsson
2016-09-30 14:16 ` Aaron Wood
2016-09-29 21:23 ` Steinar H. Gunderson
2016-09-30 1:54 ` Mario Ferreira
2016-09-30 3:50 ` Dave Täht
2016-09-30 4:29 ` Aaron Wood
2016-09-29 23:26 ` Benjamin Cronce
2016-09-30 1:58 ` Mario Ferreira [this message]
2016-10-21 8:47 ` Steinar H. Gunderson
2016-10-21 10:28 ` Eric Dumazet
2016-10-21 10:42 ` Steinar H. Gunderson
2016-10-21 10:47 ` Steinar H. Gunderson
2016-10-21 10:55 ` Eric Dumazet
2016-10-21 10:52 ` Eric Dumazet
2016-10-21 11:03 ` Steinar H. Gunderson
2016-10-21 11:40 ` Eric Dumazet
2016-10-21 11:45 ` Steinar H. Gunderson
2016-10-27 17:04 ` Steinar H. Gunderson
2016-10-27 17:31 ` Eric Dumazet
2016-10-27 17:33 ` Dave Taht
2016-10-27 17:52 ` Eric Dumazet
2016-10-27 17:59 ` Dave Taht
2016-10-27 17:57 ` Yuchung Cheng
2016-10-27 18:14 ` Dave Taht
2016-10-27 21:30 ` [Bloat] [bbr-dev] " Yuchung Cheng
2016-11-01 23:13 ` Yuchung Cheng
2016-11-01 23:49 ` Jonathan Morton
2016-11-02 9:27 ` Mikael Abrahamsson
2016-11-02 17:21 ` Klatsky, Carl
2016-11-02 18:48 ` Dave Täht
2016-11-25 12:51 ` [Bloat] " Bernd Paysan
2016-10-21 10:50 ` Zhen Cao
2016-10-27 19:25 Ingemar Johansson S
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=CAH44DxbK5n94PkBLORHfduS_cuop+nGBUeTqrPHyMzUwnpzohQ@mail.gmail.com \
--to=liouxbsd@gmail.com \
--cc=bcronce@gmail.com \
--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