From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Hagen Paul Pfeifer <hagen@jauu.net>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] ubuntu 20.4 is out
Date: Sat, 25 Apr 2020 23:10:23 -0700 [thread overview]
Message-ID: <CAA93jw5u3c+UTYgUKYJdEuTsfhSqqcP-8o5rGJ7g8CwRAaWnbA@mail.gmail.com> (raw)
In-Reply-To: <295FB76E-FCC5-4474-97F4-969AA7DB7DF4@gmx.de>
I added my comments to the bug.
On Fri, Apr 24, 2020 at 1:50 AM Sebastian Moeller <moeller0@gmx.de> wrote:
>
> Dear all,
>
>
> > On Apr 24, 2020, at 07:49, Hagen Paul Pfeifer <hagen@jauu.net> wrote:
> >
> > * Matt Taggart | 2020-04-23 15:47:19 [-0700]:
> >
> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890343#34
> >>
> >> If you have anything to add concernting changing this (or other defaults)
> >> please mail that bug. Let's get Debian up to date!
> >
> > +1
> >
> > Yes Dave, I think it's time to boost this bug report. Can you give your
> > comments and objections to the use of fifo fast? I think a little bit pressure
> > here and there and you will finally make many Debian users happier! ;-)
> >
> > I don't know if the discussion will arise that fq_codel will not be the
> > perfect fit for everybody, thus the use of "safer pfifo_fast". I think we
>
> So pfifo_fast employs a static precedence system in which high priority traffic can completely starve lower priority traffic, that is the opposite of safe, by virtue of that feature alone pfifo_fast should be relegated to those specific cases where such behaviour is desired instead of foring it upon the unwashed and enexpecting messes, no?
>
> Best Regards
> Sebastian
>
>
>
> > should take care of the average user, professionals using Debian already know
> > what to configure and how - here we should focus on the average user (Laptop,
> > Desktop).
> >
> > hgn
> >
> >
> > _______________________________________________
> > Bloat mailing list
> > Bloat@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/bloat
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
next prev parent reply other threads:[~2020-04-26 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 21:33 Dave Taht
2020-04-23 22:47 ` Matt Taggart
2020-04-24 5:49 ` Hagen Paul Pfeifer
2020-04-24 8:50 ` Sebastian Moeller
2020-04-26 6:10 ` Dave Taht [this message]
2020-04-26 11:24 ` [Bloat] [Make-wifi-fast] " Toke Høiland-Jørgensen
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=CAA93jw5u3c+UTYgUKYJdEuTsfhSqqcP-8o5rGJ7g8CwRAaWnbA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=hagen@jauu.net \
--cc=moeller0@gmx.de \
/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